# CVE-2026-56239: Capgo - Privilege Escalation via SECURITY DEFINER Function apply_usage_overage

> Authenticated users can escalate privileges to manipulate billing data for arbitrary organizations due to missing authorization checks in a database function.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-7vcj-gm5g-5g9p, GHSA-qq85-vjrq-m75g

## What is CVE-2026-56239?

CVE-2026-56239 is a high-severity vulnerability in Capgo, published on 21 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-56239?


## How do I fix CVE-2026-56239?

No fix has been published for CVE-2026-56239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56239 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56239 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56239 and fix it if it is affected.

What it is: CVE-2026-56239 is a high-severity vulnerability in Capgo, published on 21 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56239 exists.

Affected product: Capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56239/ (Markdown: https://insights.sbomify.com/CVE-2026-56239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56239
- OSV: https://osv.dev/vulnerability/CVE-2026-56239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56239/
Summaries are generated and may contain mistakes; the official description above is the record.