CVE-2026-26217: Crawl4AI Has Local File Inclusion in Docker API via file:// URLs

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 2.3%, percentile 83: FIRST’s model estimates a 2.3% chance of exploitation activity in the next 30 days, higher than 83% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes crawl4ai (PyPI) < 0.8.0, fixed in 0.8.0. Check your lockfile, including transitive dependencies.

What it is

Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /executejs, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.

From the GitHub advisory

A local file inclusion vulnerability exists in the Crawl4AI Docker API. The /executejs, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing attackers to read arbitrary files from the server filesystem.

Attack Vector:

Impact

An unauthenticated attacker can: - Read sensitive files (/etc/passwd, /etc/shadow, application configs) - Access environment variables via /proc/self/environ - Discover internal application structure - Potentially read credentials and API keys

Workarounds

Weakness type: CWE-22.

Product: crawl4ai (PyPI) · Assigned by: VulnCheck · Published: 2026-02-12

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
• FIRST EPSS (model of 2026-10-21): 2.29% probability of exploitation activity in the next 30 days; percentile 83.

Timeline

• 2026-01-16 — GitHub-reviewed advisory GHSA-vx9w-5cx4-9796 published (critical)
• 2026-02-12 — CVE record published by VulnCheck
• 2026-10-08 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. github.com github.com
2. github.com github.com

Vulnerability records

1. GitHub Advisory GHSA-vx9w-5cx4-9796 github.com
2. CVE.org record CVE-2026-26217 cve.org
3. NVD entry CVE-2026-26217 nvd.nist.gov

Other references from the CVE record and advisory

1. vulncheck.com vulncheck.com
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical PyPI advisories · Today’s Security Digest