CVE-2026-56243

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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 security control bypass vulnerability where the PostgREST/RLS plane accepts plaintext API keys through the capgkey header despite enforce_hashed_api_keys being enabled. Attackers can bypass org-level hashed-key enforcement by sending plaintext API keys directly to the PostgREST/RLS plane to access protected resources.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
19.1%
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 - Hashed API Key Enforcement Bypass via PostgREST/RLS Plane | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-hashed-api-key-enforcement-bypass-via-postgrest-rls-plane
github Patch Available🟡 PoC Available

Enforce_hashed_api_keys can be bypassed on the PostgREST/RLS plane via plaintext capgkey authentication · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-6g74-8cpq-g2c8

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

Frequently asked(5)

What is CVE-2026-56243?
CVE-2026-56243 is a high vulnerability published on June 23, 2026. Capgo before 12.128.2 contains a security control bypass vulnerability where the PostgREST/RLS plane accepts plaintext API keys through the capgkey header despite enforcehashedapi_keys being enabled. Attackers can bypass org-level hashed-key enforcement by sending plaintext API keys directly to the…
When was CVE-2026-56243 disclosed?
CVE-2026-56243 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-56243 actively exploited?
CVE-2026-56243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56243?
CVE-2026-56243 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-56243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56243, 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-56243

Explore →

Is Your Infrastructure Affected by CVE-2026-56243?

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

Start Free Scan →Browse All CVEs