CVE-2026-56260
Arbitrary file write via Crawl4AI Docker endpoints (/screenshot,/pdf) using output_path.
Is CVE-2026-56260 being exploited?
Not confirmed. CVE-2026-56260 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.
How severe is CVE-2026-56260?
CVE-2026-56260 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56260?
Yes. A fix has been recorded for CVE-2026-56260. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56260 affect?
CVE-2026-56260 affects Crawl4AI versions < 0.8.7, Crawl4AI Docker API /screenshot and /pdf endpoints, Containers/hosts running Crawl4AI with writable filesystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56260?
Upgrade to Crawl4AI 0.8.7; restrict Docker API access; validate/normalize output_path.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows attackers to write/overwrite files via unsanitized output_path, enabling data tampering, service disruption (DoS), or code modification if writable.
Patch when possible
- affected< 0.8.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.