CVE-2026-56300

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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 unauthenticated security definer RPC functions get_user_id and get_org_perm_for_apikey that expose API key validity oracles and user UUID disclosure. Unauthenticated attackers using the public API key can validate leaked keys, enumerate users and apps, and determine permission levels, significantly increasing the actionability of compromised credentials.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
26.9%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

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

Unauthenticated Supabase RPCs expose API key validity + user/org permission oracles (get_user_id, get_org_perm_for_apikey) · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-7r6g-whg3-5mm4
generic

Capgo - Unauthenticated API Key Validity and Permission Oracle via RPC Functions | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-unauthenticated-api-key-validity-and-permission-oracle-via-rpc-functions

Vendor Advisories for CVE-2026-56300(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 34× in last 7d / 34× 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-06 22:35 UTCEG score recompute
  2. 2026-07-06 22:35 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:45 UTCEG score recompute
  6. 2026-07-06 09:45 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:53 UTCEG score recompute
  10. 2026-07-05 20:53 UTCGHSA enrichment
  11. 2026-07-05 08:03 UTCEG score recompute
  12. 2026-07-05 08:03 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 19:08 UTCEG score recompute
  16. 2026-07-04 19:08 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 06:18 UTCEG score recompute
  20. 2026-07-04 06:18 UTCGHSA enrichment
  21. 2026-07-03 17:28 UTCEG score recompute
  22. 2026-07-03 17:28 UTCGHSA enrichment
  23. 2026-07-03 04:38 UTCEG score recompute
  24. 2026-07-03 04:38 UTCGHSA enrichment
  25. 2026-07-02 15:48 UTCEG score recompute
Show 9 more
  1. 2026-07-02 15:48 UTCGHSA enrichment
  2. 2026-07-02 02:58 UTCEG score recompute
  3. 2026-07-02 02:58 UTCGHSA enrichment
  4. 2026-07-01 17:06 UTCNVD updateCVSS v4 → 8.7
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 14:09 UTCEG score recompute
  7. 2026-07-01 14:09 UTCGHSA enrichment
  8. 2026-07-01 01:20 UTCEG score recompute
  9. 2026-07-01 01:19 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56300?
CVE-2026-56300 is a high vulnerability published on July 1, 2026. Capgo before 12.128.2 contains unauthenticated security definer RPC functions getuserid and getorgpermforapikey that expose API key validity oracles and user UUID disclosure. Unauthenticated attackers using the public API key can validate leaked keys, enumerate users and apps, and determine…
When was CVE-2026-56300 disclosed?
CVE-2026-56300 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-56300 actively exploited?
CVE-2026-56300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56300?
CVE-2026-56300 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56300, 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-56300

Explore →

Is Your Infrastructure Affected by CVE-2026-56300?

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

Start Free Scan →Browse All CVEs