CVE-2026-56265

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-38170 (ENISA EUVD) · GHSA-8qrg-7j2f-rf2h (GitHub Security Advisories) · PYSEC-2026-229 (OSV.dev) · PYSEC-2026-230 (OSV.dev) · PYSEC-2026-239 (OSV.dev) · PYSEC-2026-3443 (OSV.dev) · PYSEC-2026-3449 (OSV.dev) · PYSEC-2026-596 (OSV.dev) · PYSEC-2026-798 (OSV.dev)Source: ENISA EUVD

9.8EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.6%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Crawl4AI before 0.8.7 contains an authentication bypass vulnerability due to a hardcoded default JWT signing key in the Docker API server. Attackers who know the default key can forge valid authentication tokens for any user, bypassing authentication and gaining full access to protected functionality.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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
2.6%
EPSS %ILE
85th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (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.

The score's inputs: 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 21, 2026

Last Modified

November 8, 2026

Advisory Details (3)

Auto-updated Nov 8, 2026
Patch available. Sources: github.
Web page

Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crawl4ai-authentication-bypass-via-hardcoded-jwt-signing-key
Web page

GitHub - unclecode/crawl4ai: Official Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it. · 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-56265(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipcrawl4ai @ 0.8.7 (fixes < 0.8.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 15× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 544 rows 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 444 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 10:51 UTCEchelonGraph re-scored
  2. 2026-11-13 10:51 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  4. 2026-11-12 11:32 UTCEchelonGraph re-scored
  5. 2026-11-12 11:32 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  7. 2026-11-11 12:13 UTCEchelonGraph re-scored
  8. 2026-11-11 12:13 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-10 16:44 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  10. 2026-11-10 12:54 UTCEchelonGraph re-scored
  11. 2026-11-10 12:54 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  13. 2026-11-09 13:35 UTCEchelonGraph re-scored
  14. 2026-11-09 13:35 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  16. 2026-11-08 14:16 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-08 02:25 UTCEchelonGraph re-scored
  18. 2026-11-08 02:25 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-07 16:39 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  20. 2026-11-07 03:06 UTCEchelonGraph re-scored
  21. 2026-11-07 03:06 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-06 16:38 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  23. 2026-11-06 12:25 UTCOSV refresh
  24. 2026-11-06 03:47 UTCEchelonGraph re-scored
  25. 2026-11-06 03:47 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-05 16:38 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  2. 2026-11-05 04:28 UTCEchelonGraph re-scored
  3. 2026-11-05 04:28 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-04 16:36 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  5. 2026-11-04 05:09 UTCEchelonGraph re-scored
  6. 2026-11-04 05:09 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-03 16:48 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  8. 2026-11-03 05:50 UTCEchelonGraph re-scored
  9. 2026-11-03 05:50 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-02 16:45 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  11. 2026-11-02 06:31 UTCEchelonGraph re-scored
  12. 2026-11-02 06:30 UTCGHSA enrichmentGHSA-8qrg-7j2f-rf2h · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  14. 2026-11-01 07:11 UTCEchelonGraph re-scored
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  16. 2026-10-31 07:50 UTCEchelonGraph re-scored
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  18. 2026-10-30 08:31 UTCEchelonGraph re-scored
  19. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  20. 2026-10-29 09:12 UTCEchelonGraph re-scored
  21. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  22. 2026-10-28 09:53 UTCEchelonGraph re-scored
  23. 2026-10-27 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  24. 2026-10-27 09:42 UTCEchelonGraph re-scored
  25. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  26. 2026-10-26 10:23 UTCEchelonGraph re-scored
  27. 2026-10-25 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  28. 2026-10-25 14:18 UTCEchelonGraph re-scored
  29. 2026-10-25 11:05 UTCEchelonGraph re-scored
  30. 2026-10-24 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  31. 2026-10-24 11:46 UTCEchelonGraph re-scored
  32. 2026-10-23 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  33. 2026-10-23 12:27 UTCEchelonGraph re-scored
  34. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  35. 2026-10-22 13:06 UTCEchelonGraph re-scored
  36. 2026-10-21 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  37. 2026-10-21 13:44 UTCEchelonGraph re-scored
  38. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  39. 2026-10-20 14:24 UTCEchelonGraph re-scored
  40. 2026-10-19 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  41. 2026-10-19 13:24 UTCEchelonGraph re-scored
  42. 2026-10-18 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  43. 2026-10-18 03:29 UTCEchelonGraph re-scored
  44. 2026-10-17 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  45. 2026-10-17 13:43 UTCEchelonGraph re-scored
  46. 2026-10-16 16:42 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  47. 2026-10-16 14:23 UTCEchelonGraph re-scored
  48. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  49. 2026-10-15 14:34 UTCEchelonGraph re-scored
  50. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  51. 2026-10-14 09:09 UTCEchelonGraph re-scored
  52. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  53. 2026-10-13 06:09 UTCEchelonGraph re-scored
  54. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  55. 2026-10-12 15:55 UTCEchelonGraph re-scored
  56. 2026-10-11 19:38 UTCEchelonGraph re-scored
  57. 2026-10-11 16:53 UTCEchelonGraph re-scored
  58. 2026-10-11 14:16 UTCEchelonGraph re-scored
  59. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  60. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  61. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  62. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  63. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  64. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  65. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  66. 2026-10-03 14:26 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  67. 2026-10-03 13:09 UTCOSV refresh
  68. 2026-10-02 17:56 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  69. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  70. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  71. 2026-09-29 15:22 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  72. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  73. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  74. 2026-09-26 15:59 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  75. 2026-09-24 14:04 UTCEPSS rescoreEPSS 2.6% · 84th 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-56265.yaml
    Published Aug 19, 2026

    Crawl4AI < 0.8.7 - Hardcoded JWT Signing Key Authentication Bypass

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56265?
CVE-2026-56265 is a critical-severity vulnerability; its CVE record was published on June 21, 2026. Crawl4AI before 0.8.7 contains an authentication bypass vulnerability due to a hardcoded default JWT signing key in the Docker API server. Attackers who know the default key can forge valid authentication tokens for any user, bypassing authentication and gaining full access to protected…
When was CVE-2026-56265 made public?
CVE-2026-56265 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 21, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2026-56265 actively exploited?
CVE-2026-56265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56265?
CVE-2026-56265 has a CVSS base score of 9.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-56265?
A fix for CVE-2026-56265 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56265 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-56265

Explore →

Is Your Infrastructure Affected by CVE-2026-56265?

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

Book a Demo →Browse All CVEs