CVE-2026-56303

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-11. 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 weekElevated
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 an information disclosure vulnerability in the find_apikey_by_value PostgreSQL function marked SECURITY DEFINER and executable by the anon role. Unauthenticated attackers can call this function via the /rest/v1/rpc/find_apikey_by_value endpoint to retrieve sensitive API key metadata including user_id, mode, org scoping, and expiration details when supplied a valid key value.

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

Published

July 11, 2026

Last Modified

July 13, 2026

Advisory Details (2)

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

Capgo - Unauthenticated API Key Metadata Disclosure via SECURITY DEFINER RPC Function | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-unauthenticated-api-key-metadata-disclosure-via-security-definer-rpc-function
github Patch Available🟡 PoC Available

Unauthenticated SECURITY DEFINER RPC find_apikey_by_value Exposes API Key Metadata to anon · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-2xjq-h43m-592f

Vendor Advisories for CVE-2026-56303(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 25× in last 7d / 25× 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-15 18:04 UTCEG score recompute
  2. 2026-07-15 18:04 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 05:31 UTCEG score recompute
  6. 2026-07-15 05:31 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-14 16:56 UTCEG score recompute
  10. 2026-07-14 16:56 UTCGHSA enrichment
  11. 2026-07-14 04:23 UTCEG score recompute
  12. 2026-07-14 04:23 UTCGHSA enrichment
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 15:48 UTCEG score recompute
  15. 2026-07-13 15:48 UTCGHSA enrichment
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 03:14 UTCEG score recompute
  19. 2026-07-13 03:14 UTCGHSA enrichment
  20. 2026-07-12 14:40 UTCEG score recompute
  21. 2026-07-12 14:40 UTCGHSA enrichment
  22. 2026-07-12 02:07 UTCEG score recompute
  23. 2026-07-12 02:07 UTCGHSA enrichment
  24. 2026-07-11 13:33 UTCEG score recompute
  25. 2026-07-11 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56303?
CVE-2026-56303 is a high vulnerability published on July 11, 2026. Capgo before 12.128.2 contains an information disclosure vulnerability in the findapikeybyvalue PostgreSQL function marked SECURITY DEFINER and executable by the anon role. Unauthenticated attackers can call this function via the /rest/v1/rpc/findapikeybyvalue endpoint to retrieve sensitive API key…
When was CVE-2026-56303 disclosed?
CVE-2026-56303 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56303 actively exploited?
CVE-2026-56303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56303?
CVE-2026-56303 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56303, 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-56303

Explore →

Is Your Infrastructure Affected by CVE-2026-56303?

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