CVE-2026-56261

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-10. The CNA's CVSS baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
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 (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints, which accept webhook URLs without destination validation. An attacker can supply webhook URLs pointing to private or internal IP ranges, Docker networks, or cloud metadata endpoints (e.g. 169.254.169.254), causing the server to make requests to internal services and potentially expose cloud metadata.

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 partial (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
42nd
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 partial (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)14 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 partial (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

July 10, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
Patch available. Sources: github.
Web page

Crawl4AI - Server-Side Request Forgery via Webhook URLs | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-server-side-request-forgery-via-webhook-urls
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
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

Vendor Advisories for CVE-2026-56261(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 11× in last 7d / 40× 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 100 of 233 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. None are among the latest 100 rows. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56261?
CVE-2026-56261 is a high-severity vulnerability; its CVE record was published on July 10, 2026. Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints, which accept webhook URLs without destination validation. An attacker can supply webhook URLs pointing to private or internal IP ranges, Docker networks,…
When was CVE-2026-56261 made public?
CVE-2026-56261 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 July 10, 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-56261 actively exploited?
CVE-2026-56261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56261?
CVE-2026-56261 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-56261?
A fix for CVE-2026-56261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56261 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-56261

Explore →

Is Your Infrastructure Affected by CVE-2026-56261?

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

Book a Demo →Browse All CVEs