# CVE-2026-56226: Capgo - Unauthenticated Organization Data Disclosure via get_orgs_v6 RPC

> Unauthenticated attackers can retrieve sensitive organization and user PII by exploiting an exposed RPC function 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:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-fw56-3v5m-f44w, GHSA-m7mm-35v3-82f4

## What is CVE-2026-56226?

CVE-2026-56226 is a high-severity vulnerability in Cap-go capgo, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Capgo (Cap-go/capgo) before 12.128.2 exposes the Supabase PostgREST RPC function public.get_orgs_v6(userid uuid), which is SECURITY DEFINER and granted to the anon role, allowing unauthenticated access. Because the function accepts a caller-supplied user UUID without verifying it matches the authenticated user, an attacker using only the public publishable API key can query POST /rest/v1/rpc/get_orgs_v6 with an arbitrary user UUID to retrieve that user's organization membership, roles, subscription/trial metadata, and management_email (PII).

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

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


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

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

## Is CVE-2026-56226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56226 is a high-severity vulnerability in Cap-go capgo, published on 8 Jul 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-56226 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-56226/ (Markdown: https://insights.sbomify.com/CVE-2026-56226/index.md)
```

## Sources

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

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