CVE-2026-56266

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
8.6EG
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: 0.5%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Crawl4AI before 0.8.7 contains a server-side request forgery vulnerability in the /crawl, /crawl/stream, /md, and /llm endpoints that fetch arbitrary user-supplied URLs without validation. Unauthenticated attackers can bypass the internal-address blocklist using IPv6-mapped IPv4 addresses to reach internal services and cloud metadata endpoints.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation0.5% × 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
0.5%
EPSS %ILE
39th
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

June 16, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
Web page

Crawl4AI - Server-Side Request Forgery via Direct Crawl Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-server-side-request-forgery-via-direct-crawl-endpoints
Web page

GitHub - unclecode/crawl4ai: 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & Scraper. Don't be shy, join here: https://discord.gg/jP8KfhDhyN · GitHub

https://github.com/unclecode/crawl4ai
GitHub advisoryMentions a patch (unverified)

Multiple Docker API Vulnerabilities - File Write, SSRF, Auth Bypass, XSS, JS Execution · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-365w-hqf6-vxfg

Vendor Advisories for CVE-2026-56266(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.8.6 (64 versions)
  • every version up to 0.8.7: fixed in 0.8.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 31× 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 99 of 154 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 55 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56266?
CVE-2026-56266 is a high-severity vulnerability; its CVE record was published on June 16, 2026. Crawl4AI before 0.8.7 contains a server-side request forgery vulnerability in the /crawl, /crawl/stream, /md, and /llm endpoints that fetch arbitrary user-supplied URLs without validation. Unauthenticated attackers can bypass the internal-address blocklist using IPv6-mapped IPv4 addresses to reach…
When was CVE-2026-56266 made public?
CVE-2026-56266 was made public on June 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 16, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-56266 actively exploited?
CVE-2026-56266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56266?
CVE-2026-56266 has a CVSS base score of 8.6 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-56266?
A fix for CVE-2026-56266 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56266 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-56266

Explore →

Is Your Infrastructure Affected by CVE-2026-56266?

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

Book a Demo →Browse All CVEs