Is CVE-2026-56260 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56260 being exploited in the wild.

How severe is CVE-2026-56260?

Critical severity, with a CVSS score of 9.1, published 12 July 2026.

Which products and versions are affected?

crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.8.7.

Is there a fix for CVE-2026-56260?

Yes. crawl4ai (PyPI): upgrade to 0.8.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56260 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-56260?

Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56260: Crawl4AI arbitrary file write in Docker API server screenshot and pdf endpoints

CVE-2026-56260 · Severity: critical · CVSS 9.1 · Published 2026-07-12

Crawl4AI is an open-source web crawling and scraping tool designed for use with Large Language Models (LLMs). A security flaw in its Docker API server allows an attacker to write files to any location on the server's filesystem that the application has permission to access. This could be used to overwrite critical system files, leading to a complete shutdown of the service or unauthorized modification of data.

Technologies: crawl4ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-56260 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56260 being exploited in the wild.
How severe is CVE-2026-56260?: Critical severity, with a CVSS score of 9.1, published 12 July 2026.
Which products and versions are affected?: crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.8.7.
Is there a fix for CVE-2026-56260?: Yes. crawl4ai (PyPI): upgrade to 0.8.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56260 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-56260?: Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

crawl4ai (PyPI): upgrade to 0.8.7 or later
```
pip install "crawl4ai>=0.8.7"
```

Technical details

An arbitrary file write vulnerability exists in Crawl4AI's Docker API server within the /screenshot and /pdf endpoints. The root cause is a lack of validation for the 'output_path' parameter, which allows attackers to provide absolute paths or path traversal sequences (e.g., '../'). An unauthenticated remote attacker can exploit this to write or overwrite files anywhere the application user has write access. This can result in a Denial of Service (DoS) by overwriting critical configuration or system files. The issue is fixed in version 0.8.7 by implementing path validation that restricts writes to a specific output directory and rejects traversal sequences.

Affected products

unclecode Crawl4AI < 0.8.7

Identifiers

CVE-2026-56260
GHSA-365w-hqf6-vxfg
GHSA-8qrg-7j2f-rf2h
PYSEC-2026-229
PYSEC-2026-230
PYSEC-2026-239
PYSEC-2026-3443
PYSEC-2026-3449
PYSEC-2026-596
PYSEC-2026-798

Timeline

2026-06-02: advisory: Vendor security advisory published via GitHub (GHSA-365w-hqf6-vxfg)
2026-07-12: disclosed: CVE-2026-56260 published to NVD
2026-08-07: patched: Vulnerability fixed in version 0.8.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.