# CVE-2026-56242: Capgo - Unauthenticated API Key Validity Oracle and User Identity Disclosure via get_identity_apikey_only RPC

> Unauthenticated attackers can validate API keys and disclose user identities via an exposed RPC function, potentially leading to further data exposure.

- **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:** 21 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-fhgj-7376-qxwx, GHSA-wc33-3x6m-7v3x

## What is CVE-2026-56242?

CVE-2026-56242 is a high-severity vulnerability in Capgo, published on 21 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 unauthenticated security definer RPC function get_identity_apikey_only that returns the owning user_id for supplied API keys, creating an API key validity oracle and user identity disclosure primitive. Attackers can call this endpoint with valid or invalid API keys to confirm key validity and map keys to user identifiers, then chain results into other exposed RPCs like get_orgs_v6 to retrieve organization membership and management email PII.

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

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


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

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

## Is CVE-2026-56242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56242 is a high-severity vulnerability in Capgo, published on 21 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-56242 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-56242/ (Markdown: https://insights.sbomify.com/CVE-2026-56242/index.md)
```

## Sources

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

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