CVE-2026-56310

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% 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
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

Cap-go before 12.128.2 contains an authorization bypass vulnerability in the GET /organization/members endpoint that allows org-limited API keys to bypass limited_to_orgs restrictions. Attackers with org-limited API keys can read membership data including uid, email, image_url, role, and is_tmp from organizations outside their assigned scope.

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
8.0%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

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

Org-limited API keys can bypass limited_to_orgs and read other organizations’ member data via GET /organization/members · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-q7xv-p34q-v365
generic

Cap-go - Authorization Bypass in Organization Members Endpoint via API Key Scope Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cap-go-authorization-bypass-in-organization-members-endpoint-via-api-key-scope-bypass

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 42× 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 05:46 UTCEPSS rescore
  2. 2026-07-12 01:27 UTCEG score recompute
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 23:20 UTCEG score recompute
  6. 2026-07-09 21:12 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 19:06 UTCEG score recompute
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-07 16:59 UTCEG score recompute
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 13:23 UTCEG score recompute
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 10:54 UTCEG score recompute
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 08:45 UTCEG score recompute
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 17 more
  1. 2026-07-03 06:38 UTCEG score recompute
  2. 2026-07-02 04:31 UTCEG score recompute
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-07-01 02:24 UTCEG score recompute
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 00:17 UTCEG score recompute
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-28 22:10 UTCEG score recompute
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 20:03 UTCEG score recompute
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-26 17:54 UTCEG score recompute
  16. 2026-06-25 15:48 UTCEG score recompute
  17. 2026-06-25 15:47 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56310?
CVE-2026-56310 is a medium vulnerability published on June 24, 2026. Cap-go before 12.128.2 contains an authorization bypass vulnerability in the GET /organization/members endpoint that allows org-limited API keys to bypass limitedtoorgs restrictions. Attackers with org-limited API keys can read membership data including uid, email, imageurl, role, and istmp from…
When was CVE-2026-56310 disclosed?
CVE-2026-56310 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-56310 actively exploited?
CVE-2026-56310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56310?
CVE-2026-56310 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-56310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56310, 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-56310

Explore →

Is Your Infrastructure Affected by CVE-2026-56310?

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

Start Free Scan →Browse All CVEs