Capgo before 12.128.2 contains a potential privilege escalation vulnerability in the public.apply_usage_overage SECURITY DEFINER function, which performs sensitive billing operations without enforcing internal authorization checks (no validation of auth.uid(), org membership, or check_min_rights). Because the function runs with the owner's privileges, it bypasses Row Level Security. If EXECUTE permission is available to the authenticated or anon roles (explicitly or via default privileges), an authenticated user could invoke it via Supabase RPC to manipulate billing data for arbitrary organizations, including unauthorized credit depletion and fraudulent overage event insertion.
CVE-2026-56239
Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-21. a secondary CVSS source baseline 7.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(high)
- EPSS
- 9.9%
- KEV
- Not listed
Published
June 21, 2026
Last Modified
June 24, 2026
Advisory Details (2)
Auto-updated Jun 22, 2026Capgo - Privilege Escalation via SECURITY DEFINER Function apply_usage_overage | Advisories | VulnCheck
https://www.vulncheck.com/advisories/capgo-privilege-escalation-via-security-definer-function-apply-usage-overagePotential Privilege Escalation via SECURITY DEFINER function apply_usage_overage allowing unauthorized billing manipulation · Advisory · Cap-go/capgo · GitHub
https://github.com/Cap-go/capgo/security/advisories/GHSA-qq85-vjrq-m75gVendor Advisories for CVE-2026-56239(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 34× in last 7d / 79× 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.
- 2026-07-06 21:46 UTCEG score recompute
- 2026-07-06 21:46 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 08:42 UTCEG score recompute
- 2026-07-06 08:42 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 19:27 UTCEG score recompute
- 2026-07-05 19:27 UTCGHSA enrichment
- 2026-07-05 06:25 UTCEG score recompute
- 2026-07-05 06:25 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 17:20 UTCEG score recompute
- 2026-07-04 17:20 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:19 UTCEG score recompute
- 2026-07-04 04:18 UTCGHSA enrichment
- 2026-07-03 14:58 UTCEG score recompute
- 2026-07-03 14:58 UTCGHSA enrichment
- 2026-07-03 01:54 UTCEG score recompute
- 2026-07-03 01:54 UTCGHSA enrichment
- 2026-07-02 12:51 UTCEG score recompute
Show 54 moreShow fewer
- 2026-07-02 12:51 UTCGHSA enrichment
- 2026-07-01 23:49 UTCEG score recompute
- 2026-07-01 23:49 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 10:47 UTCEG score recompute
- 2026-07-01 10:47 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 21:45 UTCEG score recompute
- 2026-06-30 21:45 UTCGHSA enrichment
- 2026-06-30 08:43 UTCEG score recompute
- 2026-06-30 08:43 UTCGHSA enrichment
- 2026-06-29 19:41 UTCEG score recompute
- 2026-06-29 19:41 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 06:38 UTCEG score recompute
- 2026-06-29 06:38 UTCGHSA enrichment
- 2026-06-28 17:36 UTCEG score recompute
- 2026-06-28 17:35 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:30 UTCEG score recompute
- 2026-06-28 04:30 UTCGHSA enrichment
- 2026-06-27 15:28 UTCEG score recompute
- 2026-06-27 15:28 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 02:25 UTCEG score recompute
- 2026-06-27 02:25 UTCGHSA enrichment
- 2026-06-26 13:23 UTCEG score recompute
- 2026-06-26 13:23 UTCGHSA enrichment
- 2026-06-26 00:21 UTCEG score recompute
- 2026-06-26 00:21 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 11:13 UTCEG score recompute
- 2026-06-25 11:13 UTCGHSA enrichment
- 2026-06-24 22:11 UTCEG score recompute
- 2026-06-24 22:11 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 09:10 UTCEG score recompute
- 2026-06-24 09:10 UTCGHSA enrichment
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 20:08 UTCEG score recompute
- 2026-06-23 20:08 UTCGHSA enrichment
- 2026-06-23 07:03 UTCEG score recompute
- 2026-06-23 07:02 UTCGHSA enrichment
- 2026-06-22 19:39 UTCNVD updateCVSS v4 → 7.2
- 2026-06-22 17:58 UTCEG score recompute
- 2026-06-22 17:57 UTCGHSA enrichment
- 2026-06-22 04:44 UTCEG score recompute
- 2026-06-22 04:43 UTCGHSA enrichment
- 2026-06-21 15:38 UTCEG score recompute
- 2026-06-21 15:38 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-56239?
When was CVE-2026-56239 disclosed?
Is CVE-2026-56239 actively exploited?
What is the CVSS score of CVE-2026-56239?
How do I remediate CVE-2026-56239?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56239
Is Your Infrastructure Affected by CVE-2026-56239?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.