# CVE-2026-56237: Capgo - Unauthenticated API Key Generation via Client-Side Parameter Manipulation

> Attackers can generate arbitrary API keys by manipulating client-side parameters, bypassing authentication to access protected endpoints.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-22w2-mx2h-4fr7

## What is CVE-2026-56237?

CVE-2026-56237 is a critical authentication bypass vulnerability in Capgo, published on 24 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 a broken authentication vulnerability in its API key generation mechanism. API keys are exposed in frontend requests, and the backend fails to validate that keys are securely generated and bound to the authenticated user. An attacker can tamper with the API key parameter in the generation request and supply arbitrary values, generating custom API keys without proper authorization, which can lead to unauthorized access to protected endpoints.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-56237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56237 is a critical authentication bypass vulnerability in Capgo, published on 24 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-56237 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-56237/ (Markdown: https://insights.sbomify.com/CVE-2026-56237/index.md)
```

## Sources

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

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