# CVE-2026-56225: Capgo - Authorization Bypass in API Key Management via App-Limited Keys

> Attackers with app-scoped API keys can bypass authorization checks to enumerate, update, or delete other account-level API keys.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-44jx-wxxg-x6pv, GHSA-hwc7-j2p6-43xp

## What is CVE-2026-56225?

CVE-2026-56225 is a high-severity missing authorization vulnerability in Capgo, published on 23 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 an authorization bypass vulnerability in its public API key management handlers (get/put/delete/post). API keys created with mode=all but restricted to a single app via limited_to_apps are only checked for limited_to_orgs and not for limited_to_apps, so an app-scoped key can enumerate, update, and delete sibling API keys belonging to the same account that are outside its declared app scope, enabling tampering with account-level credentials.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-56225 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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