# CVE-2026-56234: Capgo - Password Spraying via Public-Key Accessible Credential Validation Endpoint

> Attackers can perform password spraying against an unauthenticated endpoint to compromise user accounts in Capgo.

- **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:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-74wf-7q7r-hjxr, GHSA-f6v3-xv4g-79h5

## What is CVE-2026-56234?

CVE-2026-56234 is a medium-severity authentication bypass vulnerability in Capgo, published on 23 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 credential validation vulnerability in the POST /functions/v1/private/validate_password_compliance endpoint that is callable using only the public Supabase key without authentication. The endpoint is CORS-permissive with wildcard origin allowance and lacks rate limiting, enabling attackers to perform password spraying and credential stuffing attacks to compromise user accounts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-56234 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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