# CVE-2026-56305: Capgo - Authentication Bypass in Password Change via Missing Current Password Validation

> Attackers with session access can change user passwords without current password validation, leading to account takeover and user lockout.

- **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:** 10 Jul 2026
- **Updated:** 4 Oct 2026
- **Also known as:** GHSA-j3rw-h6r5-mm7x, GHSA-rjr5-qxqj-cx8g

## What is CVE-2026-56305?

CVE-2026-56305 is a high-severity authentication bypass vulnerability in Capgo, published on 10 Jul 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 authentication bypass vulnerability in the password change endpoint that allows attackers to change user passwords without requiring current password confirmation. Attackers with temporary session access can exploit this flaw to permanently lock out legitimate users and achieve full account takeover.

Weakness: CWE-620 (Unverified Password Change)

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


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

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

## Is CVE-2026-56305 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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