CVE-2026-56230

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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 contains a broken object level authorization vulnerability in middlewareKey() that accepts the client-controlled x-limited-key-id header without validating ownership, allowing authenticated users to adopt cross-tenant limited keys. Attackers can supply another tenant's limited key ID to bypass authorization checks and access unauthorized cross-tenant resources across multiple API endpoints.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
24.1%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Capgo - Broken Object Level Authorization via x-limited-key-id Header | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-broken-object-level-authorization-via-x-limited-key-id-header
github Patch Available🟡 PoC Available

High Severity BOLA/IDOR: x-limited-key-id enables cross-tenant limited-key adoption in middlewareKey() · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-cppm-733w-hg86

Vendor Advisories for CVE-2026-56230(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 38× 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-07 06:25 UTCEG score recompute
  2. 2026-07-07 06:25 UTCGHSA enrichment
  3. 2026-07-06 18:54 UTCEG score recompute
  4. 2026-07-06 18:54 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 07:27 UTCEG score recompute
  8. 2026-07-06 07:27 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 20:00 UTCEG score recompute
  12. 2026-07-05 20:00 UTCGHSA enrichment
  13. 2026-07-05 08:32 UTCEG score recompute
  14. 2026-07-05 08:32 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 21:04 UTCEG score recompute
  18. 2026-07-04 21:04 UTCGHSA enrichment
  19. 2026-07-04 09:37 UTCEG score recompute
  20. 2026-07-04 09:37 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 22:09 UTCEG score recompute
  24. 2026-07-03 22:09 UTCGHSA enrichment
  25. 2026-07-03 10:41 UTCEG score recompute
Show 13 more
  1. 2026-07-03 10:41 UTCGHSA enrichment
  2. 2026-07-02 23:13 UTCEG score recompute
  3. 2026-07-02 23:13 UTCGHSA enrichment
  4. 2026-07-02 11:46 UTCEG score recompute
  5. 2026-07-02 11:46 UTCGHSA enrichment
  6. 2026-07-02 00:19 UTCEG score recompute
  7. 2026-07-02 00:18 UTCGHSA enrichment
  8. 2026-07-01 17:06 UTCNVD updateCVSS v4 → 8.7
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 12:49 UTCEG score recompute
  11. 2026-07-01 12:48 UTCGHSA enrichment
  12. 2026-07-01 01:20 UTCEG score recompute
  13. 2026-07-01 01:20 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56230?
CVE-2026-56230 is a high vulnerability published on July 1, 2026. Capgo before 12.128.2 contains a broken object level authorization vulnerability in middlewareKey() that accepts the client-controlled x-limited-key-id header without validating ownership, allowing authenticated users to adopt cross-tenant limited keys. Attackers can supply another tenant's limited…
When was CVE-2026-56230 disclosed?
CVE-2026-56230 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56230 actively exploited?
CVE-2026-56230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56230?
CVE-2026-56230 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56230, 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-56230

Explore →

Is Your Infrastructure Affected by CVE-2026-56230?

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

Start Free Scan →Browse All CVEs