CVE-2026-26217

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
78%
KEV
Not listed

Published

February 12, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jun 8, 2026
Patch available. Sources: github.
generic

Crawl4AI < 0.8.0 Docker API Local File Inclusion via file URL Handling | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-docker-api-local-file-inclusion-via-file-url-handling
github Patch Available

Local File Inclusion in Docker API via file:// URLs · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-vx9w-5cx4-9796
generic

crawl4ai/docs/blog/release-v0.8.0.md at main · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/blob/main/docs/blog/release-v0.8.0.md

Vendor Advisories for CVE-2026-26217(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
crawl4ai0.3.0 ... 0.7.8 (61 versions)0.8.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-01 04:39 UTCEPSS rescore
  2. 2026-08-31 19:04 UTCOSV refresh
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:48 UTCEPSS rescore
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 10:14 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 02:31 UTCEG score recompute
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 13:42 UTCEPSS rescore
  23. 2026-08-11 08:56 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 14:54 UTCEG score recompute
Show 75 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 22:03 UTCEG score recompute
  4. 2026-08-06 13:46 UTCEPSS rescore
  5. 2026-08-06 03:56 UTCEG score recompute
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-03 10:36 UTCEPSS rescore
  9. 2026-08-02 20:43 UTCEG score recompute
  10. 2026-08-02 02:26 UTCEPSS rescore
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-07-30 16:27 UTCEPSS rescore
  13. 2026-07-30 01:30 UTCEPSS rescore
  14. 2026-07-28 15:36 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-25 14:17 UTCEPSS rescore
  19. 2026-07-24 14:17 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:07 UTCEG score recompute▼ 1.10
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-22 14:08 UTCEPSS rescore
  25. 2026-07-21 15:24 UTCEPSS rescore
  26. 2026-07-21 15:24 UTCEPSS rescore
  27. 2026-07-20 17:08 UTCEPSS rescore
  28. 2026-07-20 17:08 UTCEPSS rescore
  29. 2026-07-19 14:31 UTCEPSS rescore
  30. 2026-07-19 14:31 UTCEPSS rescore
  31. 2026-07-19 02:29 UTCEPSS rescore
  32. 2026-07-18 10:04 UTCEPSS rescore
  33. 2026-07-18 10:04 UTCEPSS rescore
  34. 2026-07-17 14:59 UTCOSV refresh
  35. 2026-07-16 17:03 UTCEPSS rescore
  36. 2026-07-16 17:03 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-14 17:20 UTCNVD updateCVSS v3 → 7.5
  42. 2026-07-13 22:30 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-12 05:46 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-09 19:10 UTCEPSS rescore
  49. 2026-07-08 15:15 UTCEPSS rescore
  50. 2026-07-08 15:15 UTCEPSS rescore
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-06 16:27 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 02:23 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 06:31 UTCEPSS rescore
  58. 2026-07-04 06:31 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 13:23 UTCOSV refresh
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 14:07 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-25 13:49 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-24 14:05 UTCEPSS rescore
  73. 2026-06-24 14:05 UTCEPSS rescore
  74. 2026-06-23 21:33 UTCEPSS rescore
  75. 2026-06-23 21:32 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-26217.yaml
    First seen Jan 1, 2026

    Crawl4AI < 0.8.0 - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-26217?
CVE-2026-26217 is a high vulnerability published on February 12, 2026. 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…
When was CVE-2026-26217 disclosed?
CVE-2026-26217 was first published in the National Vulnerability Database on February 12, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26217 actively exploited?
CVE-2026-26217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 21.6% of all scored CVEs.
What is the CVSS score of CVE-2026-26217?
CVE-2026-26217 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-26217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26217

Explore →

Is Your Infrastructure Affected by CVE-2026-26217?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs