CVE-2026-56245

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER record_build_time RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/record_build_time with a public API key to poison billing and quota data for any organization, enabling resource exhaustion and cross-tenant billing manipulation.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
18.7%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

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

Unauthenticated SECURITY DEFINER RPC record_build_time allows cross-tenant build-time accounting poisoning (billing/quota impact) · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-42f8-v563-5763
generic

Supabase Capgo - Unauthenticated Cross-Tenant Build-Time Accounting Poisoning via record_build_time RPC | Advisories | VulnCheck

https://www.vulncheck.com/advisories/supabase-capgo-unauthenticated-cross-tenant-build-time-accounting-poisoning-via-record-build-time-rpc

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56245?
CVE-2026-56245 is a high vulnerability published on June 24, 2026. Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER recordbuildtime RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/recordbuildtime with a public API…
When was CVE-2026-56245 disclosed?
CVE-2026-56245 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-56245 actively exploited?
CVE-2026-56245 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56245?
CVE-2026-56245 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-56245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56245, 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-56245

Explore →

Is Your Infrastructure Affected by CVE-2026-56245?

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

Start Free Scan →Browse All CVEs