CVE-2026-56259

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
8.2EG
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.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Crawl4AI before 0.8.8 contains credential exfiltration vulnerabilities in the Docker API server that allow attackers to redirect LLM API calls to attacker-controlled endpoints and read arbitrary environment variables. Attackers can exploit the unauthenticated /md, /llm, and /llm/job endpoints by supplying a malicious base_url parameter and setting api_token to env:VARIABLE_NAME to exfiltrate provider API keys and server secrets including JWT SECRET_KEY for authentication bypass.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
35th
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 12, 2026

Last Modified

September 24, 2026

Advisory Details (2)

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

Crawl4AI - LLM Credential Exfiltration via base_url and Environment Variable Resolution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-llm-credential-exfiltration-via-base-url-and-environment-variable-resolution
GitHub advisoryMentions a patch (unverified)

LLM credential exfiltration in Docker server via request base_url and env: token resolution · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-f989-c77f-r2cq

Vendor Advisories for CVE-2026-56259(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.7 (65 versions)
  • every version up to 0.8.8: fixed in 0.8.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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 230 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 130 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.4% · 35th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th 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.4% · 35th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-01 14:50 UTCEG score recompute
  19. 2026-10-01 14:50 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-28 09:40 UTCEG score recompute
  24. 2026-09-28 09:40 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-09-24 15:01 UTCEG score recompute
  3. 2026-09-24 15:01 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  4. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-24 10:27 UTCEG score recompute
  6. 2026-09-24 10:27 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-09-23 05:38 UTCEG score recompute
  9. 2026-09-23 05:38 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  10. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-09-18 05:10 UTCEG score recompute
  13. 2026-09-18 05:10 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  14. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-14 11:08 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  19. 2026-09-13 23:36 UTCEG score recompute
  20. 2026-09-13 23:36 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-13 08:06 UTCEG score recompute
  23. 2026-09-13 08:06 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  24. 2026-09-12 13:31 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  25. 2026-09-12 02:06 UTCEG score recompute
  26. 2026-09-12 02:06 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-09-08 02:19 UTCEG score recompute
  31. 2026-09-08 02:19 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-09-06 13:54 UTCEG score recompute
  34. 2026-09-06 13:54 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  36. 2026-09-05 21:34 UTCEG score recompute
  37. 2026-09-05 21:34 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  38. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  40. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  41. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  43. 2026-08-30 16:48 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  44. 2026-08-30 05:45 UTCEG score recompute
  45. 2026-08-30 05:45 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  47. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-08-27 21:37 UTCEG score recompute
  49. 2026-08-27 21:37 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  50. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  51. 2026-08-27 00:53 UTCEG score recompute
  52. 2026-08-27 00:53 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  53. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-08-26 13:49 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  55. 2026-08-26 02:42 UTCEG score recompute
  56. 2026-08-26 02:42 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-08-25 07:11 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  59. 2026-08-24 20:07 UTCEG score recompute
  60. 2026-08-24 20:07 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  61. 2026-08-24 05:07 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  62. 2026-08-23 18:03 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  63. 2026-08-23 06:58 UTCEG score recompute
  64. 2026-08-23 06:58 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  66. 2026-08-22 19:54 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  67. 2026-08-22 08:50 UTCEG score recompute
  68. 2026-08-22 08:50 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  69. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-08-21 21:46 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  71. 2026-08-21 10:41 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  72. 2026-08-20 23:31 UTCEG score recompute
  73. 2026-08-20 23:31 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2
  74. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  75. 2026-08-20 12:28 UTCGHSA enrichmentGHSA-mw9f-q68p-364x · GitHub severity HIGH · GitHub CVSS 8.2

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56259?
CVE-2026-56259 is a high-severity vulnerability; its CVE record was published on July 12, 2026. Crawl4AI before 0.8.8 contains credential exfiltration vulnerabilities in the Docker API server that allow attackers to redirect LLM API calls to attacker-controlled endpoints and read arbitrary environment variables. Attackers can exploit the unauthenticated /md, /llm, and /llm/job endpoints by…
When was CVE-2026-56259 made public?
CVE-2026-56259 was made public on June 4, 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 12, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-56259 actively exploited?
CVE-2026-56259 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56259?
CVE-2026-56259 has a CVSS base score of 8.2 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-56259?
A fix for CVE-2026-56259 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56259 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-56259

Explore →

Is Your Infrastructure Affected by CVE-2026-56259?

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

Book a Demo →Browse All CVEs