# CVE-2026-56235: Capgo - Unauthenticated Cross-Tenant Metrics Disclosure via RPC Functions

> Unauthenticated attackers can access cross-tenant usage metrics and enumerate app IDs by exploiting missing authorization checks in Capgo RPC functions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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:** 24 Jun 2026
- **Also known as:** GHSA-g938-xgc8-q827, GHSA-gfpq-vphf-6gcm

## What is CVE-2026-56235?

CVE-2026-56235 is a medium-severity missing authorization vulnerability in Cap-go 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

Cap-go capgo before 12.128.2 contains an authorization bypass in several Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) that are granted to the anon role without enforcing org membership or permission checks. An unauthenticated attacker using only the public Supabase API key (sb_publishable_*) can query arbitrary org_id values to disclose cross-tenant usage telemetry (MAU, bandwidth, installs, gets), enumerate app IDs for a target org, and determine org existence via an oracle (valid org returns metrics, invalid returns []).

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

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


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

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

## Is CVE-2026-56235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56235 is a medium-severity missing authorization vulnerability in Cap-go 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-56235 exists.

Affected product: Cap-go 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-56235/ (Markdown: https://insights.sbomify.com/CVE-2026-56235/index.md)
```

## Sources

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

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