Which products and versions are affected by CVE-2026-26217?

Affected: Crawl4ai (Kidocode). The full list is in the CVE brief.

Is CVE-2026-26217 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-26217 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-26217?

No public exploit code is known.

Is there a fix for CVE-2026-26217?

Fixed versions are available, including Crawl4ai 0.8.0.

How urgently should CVE-2026-26217 be patched?

Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Request A Demo

Vulnerability Intelligence

CVE-2026-26217

Critical

Crawl4AI Has Local File Inclusion in Docker API via file:// URLs

Published Jan 16, 2026 · Updated Oct 10, 2026 · Also known as GHSA-vx9w-5cx4-9796, PYSEC-2026-34

Key Facts

Patch in the next maintenance window

CVE-2026-26217 is a critical-severity vulnerability (CVSS 9.2 v4) affecting Crawl4ai (Kidocode).
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 2.3% probability of exploitation in the next 30 days.
Fixed versions are available, including Crawl4ai 0.8.0.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

CVSS v4

9.2

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS (30-day exploit likelihood)

2.3%

Higher than 82.9% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2026-26217 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /execute_js, /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.

Affected Products

3 affected entries in total

Product	Affected versions	Fixed in
Crawl4aiKidocode	See advisory	0.8.0

Patched Releases

Crawl4ai

0.8.0

Timeline

Publicly disclosed
Jan 16, 2026
Last updated
Oct 10, 2026

Weakness Type

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

References

5 more references in the full CVE brief

FAQ

Common Questions.

Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment.
Affected: Crawl4ai (Kidocode). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Crawl4ai 0.8.0.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Is CVE-2026-26217 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.