# CVE-2026-56308: Capgo - Insufficient Authentication in Email Change Endpoint

> Attackers with valid sessions can change account emails without re-authentication, enabling account takeover and bypassing multi-factor authentication.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-9px4-w25f-mvm4, GHSA-gxf7-q22c-vmrj

## What is CVE-2026-56308?

CVE-2026-56308 is a high-severity authentication bypass vulnerability in Capgo, published on 12 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Capgo before 12.128.2 allows email address changes without requiring current password re-authentication or verification of the existing email address. An attacker with access to a valid session cookie or authenticated browser can change the account email to gain control of account recovery and bypass multi-factor authentication protections.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-56308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56308 is a high-severity authentication bypass vulnerability in Capgo, published on 12 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56308 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-56308/ (Markdown: https://insights.sbomify.com/CVE-2026-56308/index.md)
```

## Sources

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

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