Loading vulnerability…
CVE-2026-56260 is an arbitrary file write vulnerability in Crawl4AI before version 0.8.7. The flaw affects the Docker API server's /screenshot and /pdf endpoints, where the output_path parameter is not properly validated before being resolved and opened for writing. By supplying absolute paths or directory traversal sequences, a remote attacker can cause the application to write screenshot or PDF output to arbitrary filesystem locations writable by the Crawl4AI process. This can overwrite existing files and alter application or system state. The issue is rooted in improper restriction of filesystem paths, consistent with path traversal leading to arbitrary file write.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical path traversal / arbitrary file write vulnerability in Crawl4AI's Docker API server that allows unauthenticated remote attackers to write files to arbitrary filesystem locations via the output_path parameter in the /screenshot and /pdf endpoints.
An arbitrary file write vulnerability in Crawl4AI before version 0.8.7 affecting the Docker API server's /screenshot and /pdf endpoints via the output_path parameter, enabling path traversal or absolute-path writes that can overwrite writable server files and cause denial of service.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.