CVE-2026-56248

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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.

Cap-go capgo (capgo-backend) before 12.128.12 contains an unauthenticated denial-of-service vulnerability arising from the audit_logs table's Row-Level Security (RLS) policy when accessed via the Supabase PostgREST API. Because the PostgreSQL query planner executes costly logic before RLS rejection, unfiltered queries to the public.audit_logs endpoint using the public anon key consistently trigger statement timeouts (PostgREST error 57014). Under concurrency, this exhausts database resources and causes cascading HTTP 500 failures on unrelated endpoints (e.g. /orgs), resulting in an application-layer denial of service.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
27.9%
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 - Unauthenticated Denial-of-Service via audit_logs RLS Policy | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-unauthenticated-denial-of-service-via-audit-logs-rls-policy
github Patch Available🟡 PoC Available

Unauthenticated Denial-of-Service via Supabase PostgREST audit_logs RLS policy causing database statement timeouts · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-5vgv-rqj5-5748

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

Frequently asked(5)

What is CVE-2026-56248?
CVE-2026-56248 is a high vulnerability published on June 23, 2026. Cap-go capgo (capgo-backend) before 12.128.12 contains an unauthenticated denial-of-service vulnerability arising from the auditlogs table's Row-Level Security (RLS) policy when accessed via the Supabase PostgREST API. Because the PostgreSQL query planner executes costly logic before RLS rejection,…
When was CVE-2026-56248 disclosed?
CVE-2026-56248 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-56248 actively exploited?
CVE-2026-56248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56248?
CVE-2026-56248 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56248, 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-56248

Explore →

Is Your Infrastructure Affected by CVE-2026-56248?

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