# CVE-2026-56080: Cap-go - Authentication Logic Flaw in Enforce Password Policy

> A logic flaw in Capgo's password policy enforcement causes permanent Super Admin lockout and organization denial of service after a compliant password change.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/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:** 19 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-78rv-3cqj-36xq, GHSA-q28q-5xw5-9f2r

## What is CVE-2026-56080?

CVE-2026-56080 is a medium-severity vulnerability in Cap-go capgo, published on 19 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Capgo before 12.128.2 contains a flaw in the Enforce Password Policy feature: after a Super Admin enables the policy and successfully changes their password to a compliant one, the backend does not update the password-compliance state. As a result, the backend continues to treat the account as non-compliant and repeatedly forces password-reset prompts, permanently locking the Super Admin out of organization access (organization lockout / denial of service) despite valid authentication.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-56080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56080 is a medium-severity vulnerability in Cap-go capgo, published on 19 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-56080 exists.

Affected product: Cap-go 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-56080/ (Markdown: https://insights.sbomify.com/CVE-2026-56080/index.md)
```

## Sources

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

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