CVE-2026-56225

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: 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 an authorization bypass vulnerability in its public API key management handlers (get/put/delete/post). API keys created with mode=all but restricted to a single app via limited_to_apps are only checked for limited_to_orgs and not for limited_to_apps, so an app-scoped key can enumerate, update, and delete sibling API keys belonging to the same account that are outside its declared app scope, enabling tampering with account-level credentials.

CVSS v3
8.3
EG Score
8.3(high)
EPSS
21.0%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

Capgo - Authorization Bypass in API Key Management via App-Limited Keys | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-authorization-bypass-in-api-key-management-via-app-limited-keys
github Patch Available🟡 PoC Available

App-limited all API keys can update and delete sibling account API keys outside their app scope · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-hwc7-j2p6-43xp

Vendor Advisories for CVE-2026-56225(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 36× in last 7d / 72× 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 00:04 UTCEG score recompute
  2. 2026-07-07 00:04 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:38 UTCEG score recompute
  6. 2026-07-06 11:38 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:12 UTCEG score recompute
  10. 2026-07-05 23:12 UTCGHSA enrichment
  11. 2026-07-05 10:46 UTCEG score recompute
  12. 2026-07-05 10:46 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 22:19 UTCEG score recompute
  16. 2026-07-04 22:19 UTCGHSA enrichment
  17. 2026-07-04 09:53 UTCEG score recompute
  18. 2026-07-04 09:53 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 21:24 UTCEG score recompute
  22. 2026-07-03 21:24 UTCGHSA enrichment
  23. 2026-07-03 08:59 UTCEG score recompute
  24. 2026-07-03 08:59 UTCGHSA enrichment
  25. 2026-07-02 20:32 UTCEG score recompute
Show 47 more
  1. 2026-07-02 20:32 UTCGHSA enrichment
  2. 2026-07-02 08:06 UTCEG score recompute
  3. 2026-07-02 08:06 UTCGHSA enrichment
  4. 2026-07-01 19:39 UTCEG score recompute
  5. 2026-07-01 19:39 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 07:14 UTCEG score recompute
  8. 2026-07-01 07:14 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 18:48 UTCEG score recompute
  11. 2026-06-30 18:48 UTCGHSA enrichment
  12. 2026-06-30 06:22 UTCEG score recompute
  13. 2026-06-30 06:22 UTCGHSA enrichment
  14. 2026-06-29 17:56 UTCEG score recompute
  15. 2026-06-29 17:56 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 05:30 UTCEG score recompute
  19. 2026-06-29 05:29 UTCGHSA enrichment
  20. 2026-06-28 17:02 UTCEG score recompute
  21. 2026-06-28 17:02 UTCGHSA enrichment
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:36 UTCEG score recompute
  26. 2026-06-28 04:36 UTCGHSA enrichment
  27. 2026-06-27 16:09 UTCEG score recompute
  28. 2026-06-27 16:09 UTCGHSA enrichment
  29. 2026-06-27 03:43 UTCEG score recompute
  30. 2026-06-27 03:43 UTCGHSA enrichment
  31. 2026-06-27 03:08 UTCEPSS rescore
  32. 2026-06-26 15:17 UTCEG score recompute
  33. 2026-06-26 15:17 UTCGHSA enrichment
  34. 2026-06-26 02:51 UTCEG score recompute
  35. 2026-06-26 02:51 UTCGHSA enrichment
  36. 2026-06-25 14:25 UTCEG score recompute
  37. 2026-06-25 14:25 UTCGHSA enrichment
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 01:59 UTCEG score recompute
  40. 2026-06-25 01:59 UTCGHSA enrichment
  41. 2026-06-24 14:05 UTCEPSS rescore
  42. 2026-06-24 13:33 UTCEG score recompute
  43. 2026-06-24 13:33 UTCGHSA enrichment
  44. 2026-06-24 01:07 UTCEG score recompute
  45. 2026-06-24 01:07 UTCGHSA enrichment
  46. 2026-06-23 12:42 UTCEG score recompute
  47. 2026-06-23 12:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56225?
CVE-2026-56225 is a high vulnerability published on June 23, 2026. Capgo before 12.128.2 contains an authorization bypass vulnerability in its public API key management handlers (get/put/delete/post). API keys created with mode=all but restricted to a single app via limitedtoapps are only checked for limitedtoorgs and not for limitedtoapps, so an app-scoped key…
When was CVE-2026-56225 disclosed?
CVE-2026-56225 was first published in the National Vulnerability Database on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56225 actively exploited?
CVE-2026-56225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56225?
CVE-2026-56225 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-56225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56225, 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-56225

Explore →

Is Your Infrastructure Affected by CVE-2026-56225?

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

Start Free Scan →Browse All CVEs