Security readout for executives and security teams
Plain-English summary
CVE-2026-56260 lets unauthenticated attackers make Crawl4AI’s Docker API write files to unintended server paths through screenshot or PDF generation. This can overwrite files the application user can access, causing service disruption or damaging application integrity. Supplied sources rate it critical with CVSS 9.1.
Executive priority
Treat as urgent for exposed Crawl4AI Docker API deployments. The issue is critical, unauthenticated, and can disrupt service by overwriting writable server files. Patch and restrict API exposure promptly, prioritizing internet-facing or broadly reachable internal instances.
Technical view
Crawl4AI before 0.8.7 has CWE-22 path traversal in the Docker API server’s /screenshot and /pdf endpoints. The output_path parameter accepts absolute or traversal paths without validation, enabling arbitrary file write within the application user’s filesystem permissions. CVSS is 9.1: network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Highest exposure is any Crawl4AI Docker API server reachable from untrusted networks or users, especially if /screenshot or /pdf endpoints are accessible. Internal-only deployments still matter if many users, services, or agents can reach the API.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation. Exploitation requires network access to the affected API endpoints, but not authentication according to the CVSS privileges-required rating. Impact is focused on integrity and availability, not confidentiality in the provided CVSS vector.
Researcher notes
Evidence is consistent across the CVE record, GitHub advisory reference, and VulnCheck advisory. The core weakness is unchecked path handling in output_path. Do not assume remote code execution from the supplied sources; documented impact is arbitrary file write, integrity loss, and denial of service.
Mitigation direction
- Upgrade Crawl4AI to version 0.8.7 or later.
- Restrict Docker API server access to trusted networks and authenticated callers.
- Block untrusted access to /screenshot and /pdf endpoints until patched.
- Review vendor advisory for any additional hardening guidance.
Validation and detection
- Inventory Crawl4AI deployments and identify Docker API server exposure.
- Confirm installed Crawl4AI versions; prioritize any version before 0.8.7.
- Check whether /screenshot and /pdf endpoints are reachable by untrusted users.
- Review logs for abnormal output_path values or failed file-write activity.
- Verify network controls limit API access after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-56260 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-365w-hqf6-vxfgCVE reference, VulnCheck · vendor-advisory
- https://github.com/unclecode/crawl4aiCVE reference, VulnCheck · product
- VulnCheck Advisory: Crawl4AI - Arbitrary File Write via output_path ParameterCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.