# ZITADEL's Improper Lockout Mechanism Leads to MFA Bypass

Advisory record · `GHSA-7j7j-66cv-m239`

- **Identifiers:** `GHSA-7j7j-66cv-m239` · `CVE-2024-32868` · `GO-2024-2788`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-297](https://cwe.mitre.org/data/definitions/297.html) · [CWE-307](https://cwe.mitre.org/data/definitions/307.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 25 Apr 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Apr 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/zitadel/zitadel` (Go): affected `<2.50.0`; fixed in `2.50.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> ZITADEL versions before 2.50.0 lack a lockout mechanism for time-based and one-time password checks, so repeated failed (T)OTP attempts are not limited, unlike password checks, which the admin-configurable Lockout Policy covers. The source does not describe the attacker's access requirements beyond that. Upgrade the github.com/zitadel/zitadel package to version 2.50.0 or later; no workaround is listed.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7j7j-66cv-m239)

## Sources

- [GitHub Advisory Database: GHSA-7j7j-66cv-m239](https://github.com/advisories/GHSA-7j7j-66cv-m239)
- [OSV: GHSA-7j7j-66cv-m239](https://osv.dev/vulnerability/GHSA-7j7j-66cv-m239)
- <https://github.com/zitadel/zitadel/security/advisories/GHSA-7j7j-66cv-m239>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-32868>
- <https://github.com/zitadel/zitadel>
- <https://github.com/zitadel/zitadel/releases/tag/v2.50.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-7j7j-66cv-m239>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7j7j-66cv-m239/>. Everything for agents: <https://agentprime.io/llms.txt>.
