Is CVE-2026-26217 exploited in the wild?

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

How severe is CVE-2026-26217?

High severity, with a CVSS score of 8.6, published 12 February 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-26217?

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

How is CVE-2026-26217 attacked?

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

Am I affected by CVE-2026-26217?

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-26217: unclecode Crawl4AI local file inclusion in Docker API

Q: Which products and versions are affected?

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

Q: Is there a fix for CVE-2026-26217?

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

Q: How is CVE-2026-26217 attacked?

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

Q: Am I affected by CVE-2026-26217?

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-26217 · Severity: high · CVSS 8.6 · Published 2026-02-12

Crawl4AI, a tool used for web crawling and data extraction, contains a security flaw in its Docker API deployment. This vulnerability allows an unauthorized person to remotely read sensitive files from the server's filesystem, such as system passwords, configuration files, and internal credentials. This could lead to a full compromise of the server or the exposure of private API keys and application data.

Technologies: crawl4ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-26217 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-26217 being exploited in the wild.
How severe is CVE-2026-26217?: High severity, with a CVSS score of 8.6, published 12 February 2026.
Which products and versions are affected?: crawl4ai (PyPI) < 0.8.0, ECOSYSTEM:introduced=0,fixed=0.8.0.
Is there a fix for CVE-2026-26217?: Yes. crawl4ai (PyPI): upgrade to 0.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-26217 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-26217?: 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.0 or later
```
pip install "crawl4ai>=0.8.0"
```

Technical details

A Local File Inclusion (LFI) vulnerability exists in the Docker API of Crawl4AI due to improper validation of URL schemes. The /execute_js, /screenshot, /pdf, and /html endpoints accept the 'file://' protocol, which allows an unauthenticated remote attacker to request local system files instead of remote web pages. By submitting a crafted POST request, an attacker can retrieve sensitive files such as /etc/passwd, /etc/shadow, or environment variables via /proc/self/environ. This vulnerability is classified as CWE-22 (Path Traversal) and has been addressed in version 0.8.0.

Affected products

unclecode Crawl4AI < 0.8.0

Identifiers

CVE-2026-26217
GHSA-vx9w-5cx4-9796
PYSEC-2026-34

Timeline

2026-01-16: advisory: Vendor published security advisory GHSA-vx9w-5cx4-9796
2026-02-12: disclosed: CVE-2026-26217 published to NVD
2026-02-12: patched: Version 0.8.0 released to address the vulnerability

References

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