CVE-2026-56260 Crawl4AI - Arbitrary File Write via output_path Parameter
Attackers can write arbitrary files to the server via the output_path parameter in Crawl4AI's Docker API, potentially overwriting files and causing denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-56260?
CVE-2026-56260 is a high-severity path traversal vulnerability in Crawl4AI, published on 12 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.
Weakness: CWE-22
Which versions are affected by CVE-2026-56260?
It affects 1 product.
Products include Kidocode Crawl4ai.
How do I fix CVE-2026-56260?
Upgrade to a fixed version.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-56260 being exploited?
There is no known exploitation of CVE-2026-56260 in the wild and no public exploit code.
Other vulnerabilities in Crawl4AI
- CVE-2026-57572 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args
- CVE-2026-26216 Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter
- CVE-2026-53753 Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API
- CVE-2026-57571 Crawl4AI arbitrary file write via download filename path traversal
- CVE-2026-56265 Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key