# CVE-2026-56214: Capgo - Unauthenticated Organization Enumeration and Billing Status Disclosure via Supabase RPC

> Unauthenticated attackers can enumerate organizations and reveal billing status via exposed Supabase RPC endpoints in Capgo.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-cmgw-4g6h-mpvm, GHSA-mh5p-rrhp-442q

## What is CVE-2026-56214?

CVE-2026-56214 is a high-severity vulnerability in Capgo, published on 20 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an information disclosure vulnerability in Supabase PostgREST RPC endpoints is_trial_org and is_paying_org that allows unauthenticated attackers to enumerate organizations and disclose billing status using the public sb_publishable key. Attackers can invoke these endpoints to determine organization existence via distinguishable return values and identify paying customers for targeted profiling.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-56214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56214 is a high-severity vulnerability in Capgo, published on 20 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56214 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-56214/ (Markdown: https://insights.sbomify.com/CVE-2026-56214/index.md)
```

## Sources

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

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