# CVE-2026-56228: Capgo - Denial of Service via Improper Password Policy Length Validation

> An authenticated admin can set an impossibly high minimum password length, locking out all users and causing a denial of service.

- **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:** 20 Jun 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-j8w3-fhfr-rrvp, GHSA-vhjp-62qf-33mx

## What is CVE-2026-56228?

CVE-2026-56228 is a medium-severity denial of service 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 fails to enforce a maximum value on the minimum password length field in its password policy configuration. An authenticated organization administrator can set an extremely large numeric value (e.g., billions of characters) as the minimum password length, making compliance impossible for all organization members. Once the policy is enabled, users (including administrators) are unable to change their passwords or access the organization, resulting in an organization-wide account lockout and application-level denial of service.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-56228 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56228 is a medium-severity denial of service vulnerability in Capgo, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56228 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-56228/ (Markdown: https://insights.sbomify.com/CVE-2026-56228/index.md)
```

## Sources

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

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