CVE-2026-56237

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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
Elevated

Also known asEUVD-2026-38740 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule 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: 0.5%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

Capgo before 12.128.2 contains a broken authentication vulnerability in its API key generation mechanism. API keys are exposed in frontend requests, and the backend fails to validate that keys are securely generated and bound to the authenticated user. An attacker can tamper with the API key parameter in the generation request and supply arbitrary values, generating custom API keys without proper authorization, which can lead to unauthorized access to protected endpoints.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.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.

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule 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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

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 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

🛡️ Bug Report: Unauthenticated API Key Generation & API Key Disclosure in Request · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-22w2-mx2h-4fr7
Web page

Capgo - Unauthenticated API Key Generation via Client-Side Parameter Manipulation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-unauthenticated-api-key-generation-via-client-side-parameter-manipulation

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 56× 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 195 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 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56237?
CVE-2026-56237 is a critical-severity vulnerability; its CVE record was published on June 24, 2026. Capgo before 12.128.2 contains a broken authentication vulnerability in its API key generation mechanism. API keys are exposed in frontend requests, and the backend fails to validate that keys are securely generated and bound to the authenticated user. An attacker can tamper with the API key…
When was CVE-2026-56237 made public?
CVE-2026-56237 was made public on February 10, 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 24, 2026. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56237 actively exploited?
CVE-2026-56237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56237?
CVE-2026-56237 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56237?
No fix for CVE-2026-56237 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56237

Explore →

Is Your Infrastructure Affected by CVE-2026-56237?

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

Book a Demo →Browse All CVEs