CVE-2026-56232

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_apps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
18.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

MiddlewareKey x-limited-key-id subkey scope bypass: limited_to_orgs and limited_to_apps constraints are completely ignored (+ missing validateSubkeyUser cross-tenant check) · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-2h89-vcvx-5pvh
generic

Capgo - Subkey Scope Bypass in middlewareKey via x-limited-key-id Header | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-subkey-scope-bypass-in-middlewarekey-via-x-limited-key-id-header

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 23:42 UTCEG score recompute
  4. 2026-07-14 12:24 UTCEG score recompute
  5. 2026-07-14 01:08 UTCEG score recompute
  6. 2026-07-13 22:31 UTCEPSS rescore
  7. 2026-07-13 13:48 UTCEG score recompute
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 02:31 UTCEG score recompute
  11. 2026-07-12 15:13 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 03:52 UTCEG score recompute
  14. 2026-07-11 16:36 UTCEG score recompute
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 05:20 UTCEG score recompute
  18. 2026-07-10 18:04 UTCEG score recompute
  19. 2026-07-10 06:47 UTCEG score recompute
  20. 2026-07-09 19:25 UTCEG score recompute
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 08:08 UTCEG score recompute
  24. 2026-07-08 20:51 UTCEG score recompute
  25. 2026-07-08 15:16 UTCEPSS rescore
Show 48 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-08 09:36 UTCEG score recompute
  3. 2026-07-07 22:19 UTCEG score recompute
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-07 11:02 UTCEG score recompute
  7. 2026-07-06 22:49 UTCEG score recompute
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 11:32 UTCEG score recompute
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 00:15 UTCEG score recompute
  14. 2026-07-05 12:56 UTCEG score recompute
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-05 01:39 UTCEG score recompute
  18. 2026-07-04 14:15 UTCEG score recompute
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 02:59 UTCEG score recompute
  22. 2026-07-03 15:34 UTCEG score recompute
  23. 2026-07-03 04:18 UTCEG score recompute
  24. 2026-07-02 17:02 UTCEG score recompute
  25. 2026-07-02 05:45 UTCEG score recompute
  26. 2026-07-01 18:29 UTCEG score recompute
  27. 2026-07-01 15:07 UTCEPSS rescore
  28. 2026-07-01 07:13 UTCEG score recompute
  29. 2026-06-30 23:22 UTCEPSS rescore
  30. 2026-06-30 19:55 UTCEG score recompute
  31. 2026-06-30 08:39 UTCEG score recompute
  32. 2026-06-29 21:16 UTCEG score recompute
  33. 2026-06-29 14:06 UTCEPSS rescore
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-29 09:59 UTCEG score recompute
  36. 2026-06-28 22:42 UTCEG score recompute
  37. 2026-06-28 14:07 UTCEPSS rescore
  38. 2026-06-28 11:25 UTCEG score recompute
  39. 2026-06-28 04:56 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 00:09 UTCEG score recompute
  42. 2026-06-27 12:53 UTCEG score recompute
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-27 01:37 UTCEG score recompute
  45. 2026-06-26 14:20 UTCEG score recompute
  46. 2026-06-26 03:04 UTCEG score recompute
  47. 2026-06-25 15:48 UTCEG score recompute
  48. 2026-06-25 15:47 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56232?
CVE-2026-56232 is a high vulnerability published on June 24, 2026. Capgo before 12.128.2 fails to enforce limitedtoorgs and limitedtoapps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the…
When was CVE-2026-56232 disclosed?
CVE-2026-56232 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56232 actively exploited?
CVE-2026-56232 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56232?
CVE-2026-56232 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56232, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56232?

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

Start Free Scan →Browse All CVEs