CVE-2026-56246

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: 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 access control vulnerability in the organization management API where a scoped API key (limited_to_orgs) inherits its owner-user's permissions, allowing destructive cross-organization actions. When a user is an admin in two organizations and creates a write-mode API key restricted to one organization, that key can still perform destructive operations (e.g., DELETE /organization, DELETE /organization/members) against another organization. The root cause is route-level authorization (rbac_check_permission_direct) that evaluates the key owner's user privileges before enforcing the API key's limited_to_orgs scope.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
12.8%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (2)

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

Capgo - Cross-Organization Authorization Bypass via Scoped API Key Privilege Inheritance | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-cross-organization-authorization-bypass-via-scoped-api-key-privilege-inheritance
github Patch Available🟡 PoC Available

Scoped API key can perform cross-org destructive actions by inheriting owner-user permissions · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-ccm4-hf72-p28m

Vendor Advisories for CVE-2026-56246(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 23× in last 7d / 23× 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-12 21:34 UTCEG score recompute
  2. 2026-07-12 21:34 UTCGHSA enrichment
  3. 2026-07-12 08:39 UTCEG score recompute
  4. 2026-07-12 08:39 UTCGHSA enrichment
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 19:43 UTCEG score recompute
  7. 2026-07-11 19:43 UTCGHSA enrichment
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 06:48 UTCEG score recompute
  11. 2026-07-11 06:48 UTCGHSA enrichment
  12. 2026-07-10 17:53 UTCEG score recompute
  13. 2026-07-10 17:53 UTCGHSA enrichment
  14. 2026-07-10 04:58 UTCEG score recompute
  15. 2026-07-10 04:58 UTCGHSA enrichment
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 16:02 UTCEG score recompute
  19. 2026-07-09 16:02 UTCGHSA enrichment
  20. 2026-07-09 03:05 UTCEG score recompute
  21. 2026-07-09 03:05 UTCGHSA enrichment
  22. 2026-07-08 14:07 UTCEG score recompute
  23. 2026-07-08 14:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56246?
CVE-2026-56246 is a high vulnerability published on July 8, 2026. Capgo before 12.128.2 contains a broken access control vulnerability in the organization management API where a scoped API key (limitedtoorgs) inherits its owner-user's permissions, allowing destructive cross-organization actions. When a user is an admin in two organizations and creates a…
When was CVE-2026-56246 disclosed?
CVE-2026-56246 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56246 actively exploited?
CVE-2026-56246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56246?
CVE-2026-56246 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-56246?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56246, 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-56246

Explore →

Is Your Infrastructure Affected by CVE-2026-56246?

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

Start Free Scan →Browse All CVEs