# CVE-2026-56313: Capgo - Cross-Organization Account Disruption via SSO Prelink Endpoint

> Enterprise admins can delete password identities of users in other organizations via SSO prelink endpoint, forcing account takeover or recovery.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 12 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-ppxp-w5f2-39vv, GHSA-x3vq-34gg-cwq7

## What is CVE-2026-56313?

CVE-2026-56313 is a high-severity missing authorization vulnerability in Capgo, published on 12 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 a cross-organization account disruption vulnerability in the SSO prelink endpoint that allows enterprise administrators to delete password identities of users in foreign organizations. Attackers with org.update_settings permission and an active SSO provider can call the prelink-users endpoint to permanently remove email-based authentication for any user matching the provider's email domain, forcing victims to use the attacker's SSO provider or complete password reset recovery.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-56313 being exploited?

There is no known exploitation of CVE-2026-56313 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56313 is a high-severity missing authorization vulnerability in Capgo, published on 12 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56313 in the wild and no public exploit code.

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-56313/ (Markdown: https://insights.sbomify.com/CVE-2026-56313/index.md)
```

## Sources

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

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