# CVE-2026-56212: Capgo - Improper 2FA Enforcement Logic via Team Security Settings

> Attackers can enforce mandatory 2FA on teams without having it enabled themselves, causing potential lockouts and inconsistent security enforcement.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-4f3c-ph4g-54q4, GHSA-w2cr-vcwj-69x2

## What is CVE-2026-56212?

CVE-2026-56212 is a medium-severity vulnerability in Capgo, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an authentication logic flaw: a user with permission to manage team or organization security settings can enable mandatory two-factor authentication for all team members without first enabling 2FA on their own account. The application fails to verify the initiator's 2FA status before allowing the policy change, resulting in inconsistent security enforcement, potential administrative misuse, and lockout risk for team members.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-56212 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56212 is a medium-severity vulnerability in Capgo, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56212 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-56212/ (Markdown: https://insights.sbomify.com/CVE-2026-56212/index.md)
```

## Sources

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

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