CVE-2026-56245

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists Cap-go capgo versions before 12.128.2 as affected, and Cap-go capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

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.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

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
Web page

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 11× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 150 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  5. 2026-10-12 15:40 UTCEG score recompute
  6. 2026-10-11 19:38 UTCEG score recompute
  7. 2026-10-11 16:53 UTCEG score recompute
  8. 2026-10-11 14:16 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 74 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-09-23 11:49 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-09-18 08:14 UTCEG score recompute
  6. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-14 01:57 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  12. 2026-09-13 12:11 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-08-30 20:21 UTCEG score recompute
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  26. 2026-08-28 04:51 UTCEG score recompute
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  30. 2026-08-24 22:02 UTCEG score recompute
  31. 2026-08-23 02:39 UTCEG score recompute
  32. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  33. 2026-08-22 13:18 UTCEG score recompute
  34. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  35. 2026-08-21 09:59 UTCEG score recompute
  36. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  37. 2026-08-20 07:36 UTCEG score recompute
  38. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-08-19 02:20 UTCEG score recompute
  40. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  42. 2026-08-17 00:17 UTCEG score recompute
  43. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  44. 2026-08-16 11:06 UTCEG score recompute
  45. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  46. 2026-08-15 08:43 UTCEG score recompute
  47. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  48. 2026-08-14 03:55 UTCEG score recompute
  49. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  50. 2026-08-13 01:32 UTCEG score recompute
  51. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-08-11 22:57 UTCEG score recompute
  53. 2026-08-11 09:46 UTCEG score recompute
  54. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  55. 2026-08-09 18:11 UTCEG score recompute
  56. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  57. 2026-08-09 05:00 UTCEG score recompute
  58. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  59. 2026-08-08 02:37 UTCEG score recompute
  60. 2026-08-07 00:13 UTCEG score recompute
  61. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  62. 2026-08-05 21:50 UTCEG score recompute
  63. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  64. 2026-08-04 16:59 UTCEG score recompute
  65. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  67. 2026-08-02 12:10 UTCEG score recompute
  68. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  69. 2026-08-01 09:46 UTCEG score recompute
  70. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  71. 2026-07-30 17:49 UTCEG score recompute
  72. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  73. 2026-07-30 03:30 UTCEG score recompute
  74. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile

Frequently asked(5)

What is CVE-2026-56245?
CVE-2026-56245 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-56245 was made public on March 17, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 24, 2026. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56245 actively exploited?
CVE-2026-56245 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56245?
CVE-2026-56245 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56245?
No fix for CVE-2026-56245 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists Cap-go capgo versions before 12.128.2 as affected, and Cap-go capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

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.