CVE-2026-26216

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 6.0% (93rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6.0%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
62
EG Risk 62/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation6.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
6.0%
EPSS %ILE
93rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 12, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Oct 15, 2026
Patch available. Sources: github.
Web page

Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-docker-api-unauthenticated-remote-code-execution-via-hooks-parameter
GitHub advisoryMentions a patch (unverified)

Remote Code Execution in Docker API via Hooks Parameter · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-5882-5rx9-xgxp
Web page

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-26216(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 rangeFix by version rangeDependents
crawl4ai0.3.0 ... 0.7.8 (61 versions)
  • every version up to 0.8.0: fixed in 0.8.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-17 06:59 UTCEG score recompute
  2. 2026-10-16 16:41 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  3. 2026-10-16 07:49 UTCEG score recompute
  4. 2026-10-15 16:31 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  5. 2026-10-15 06:49 UTCEG score recompute
  6. 2026-10-14 16:32 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  7. 2026-10-14 02:33 UTCEG score recompute
  8. 2026-10-13 16:33 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  9. 2026-10-12 22:46 UTCEG score recompute
  10. 2026-10-12 16:33 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  11. 2026-10-12 16:18 UTCEG score recompute
  12. 2026-10-11 20:00 UTCEG score recompute
  13. 2026-10-11 17:14 UTCEG score recompute
  14. 2026-10-11 14:45 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  18. 2026-10-08 17:11 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  19. 2026-10-08 16:42 UTCEG score recompute
  20. 2026-10-08 15:48 UTCEG score recompute
  21. 2026-10-07 23:47 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  22. 2026-10-06 15:17 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  23. 2026-10-05 17:42 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  25. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.7% · 75th percentile
Show 67 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  2. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  4. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  6. 2026-09-19 23:16 UTCOSV refresh
  7. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  8. 2026-09-17 19:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  9. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  13. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  14. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  15. 2026-09-08 22:00 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  18. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  19. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  20. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  21. 2026-09-01 04:39 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  22. 2026-09-01 02:34 UTCOSV refresh
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  28. 2026-08-25 13:48 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  29. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  30. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  31. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  32. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  33. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  34. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  35. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  36. 2026-08-16 02:14 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  37. 2026-08-15 02:12 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  39. 2026-08-14 10:14 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  41. 2026-08-13 02:31 UTCEG score recompute
  42. 2026-08-12 13:50 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  43. 2026-08-11 13:42 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  44. 2026-08-11 08:56 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  46. 2026-08-09 14:54 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  48. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  49. 2026-08-07 22:03 UTCEG score recompute
  50. 2026-08-06 13:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  51. 2026-08-06 03:56 UTCEG score recompute
  52. 2026-08-05 19:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  53. 2026-08-04 15:10 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  54. 2026-08-03 10:36 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  55. 2026-08-02 20:43 UTCEG score recompute
  56. 2026-08-02 02:26 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  57. 2026-08-01 04:16 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  58. 2026-07-30 16:27 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  59. 2026-07-30 01:30 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  60. 2026-07-28 15:36 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  61. 2026-07-26 14:54 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  62. 2026-07-25 14:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  63. 2026-07-24 14:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  64. 2026-07-23 14:18 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  65. 2026-07-23 03:07 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  67. 2026-07-21 15:24 UTCEPSS rescoreEPSS 1.6% · 72nd percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-26216.yaml
    Published Oct 2, 2026

    Crawl4AI < 0.8.0 - Unauthenticated Remote Code Execution via Hooks Parameter

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-26216?
CVE-2026-26216 is a critical-severity vulnerability; its CVE record was published on February 12, 2026. Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The import builtin was included in the allowed builtins, allowing unauthenticated remote…
When was the CVE record for CVE-2026-26216 published?
The CVE record for CVE-2026-26216 was published on February 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-26216 actively exploited?
CVE-2026-26216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.0% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26216?
CVE-2026-26216 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-26216?
A fix for CVE-2026-26216 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-26216 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-26216?

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

Book a Demo →Browse All CVEs