Quick answers
- Is CVE-2026-56258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56258 being exploited in the wild.
- How severe is CVE-2026-56258?
- High severity, with a CVSS score of 8.1, published 23 June 2026.
- Which products and versions are affected?
- crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.8.8.
- Is there a fix for CVE-2026-56258?
- Yes. crawl4ai (PyPI): upgrade to 0.8.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56258 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56258?
- 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.8 or later
pip install "crawl4ai>=0.8.8"
Technical details
Crawl4AI's Docker API server is vulnerable to an arbitrary file write via the 'output_path' parameter in the /screenshot and /pdf endpoints. The vulnerability stems from insufficient path validation in the 'validate_output_path' function, which performed string-only checks without resolving symlinks. By exploiting a time-of-check-time-of-use (TOCTOU) race condition or using symlinks within the allowed output directory, a remote, unauthenticated attacker can write files to restricted locations. If the runtime user has sufficient permissions, this can lead to remote code execution by overwriting binaries or cron jobs. Version 0.8.8 fixes this by resolving real paths during validation and using the O_NOFOLLOW flag during file writes.
Affected products
- unclecode Crawl4AI < 0.8.8
Identifiers
- CVE-2026-56258
- GHSA-7cx2-g3h9-382p
- PYSEC-2026-228
Timeline
- 2026-06-04: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: NVD publication date