Zitadel May Bypass Second Authentication Factor
Published 29 Oct 2025 · Updated 5 Nov 2025
Is your project on an affected github.com/zitadel/zitadel/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.53.6 <=2.53.9
- Fixed in
- No fix released
- Affected
- >=2.54.3 <=2.54.10
- Fixed in
- No fix released
- Affected
- >=2.55.0 <2.71.18
- Fixed in
- 2.71.18
go get github.com/zitadel/zitadel/v2@v2.71.18- Affected
- <1.80.0-v2.20.0.20251029091250-b284f8474eed
- Fixed in
- 1.80.0-v2.20.0.20251029091250-b284f8474eed
go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251029091250-b284f8474eedDetails
Summary
A vulnerability in Zitadel's token verification prematurely marked sessions as authenticated when only one factor was verified.
Impact
Zitadel provides an API for managing sessions, enabling custom login experiences in a dedicated UI or direct integration into applications. Session Tokens are issued for active sessions, which can be used as Bearer tokens to call the Zitadel API.
Starting from 2.55.0 (see other affected versions below), Zitadel only required multi factor authentication in case the login policy has either enabled requireMFA or requireMFAForLocalUsers. If a user has set up MFA without this requirement, Zitadel would consider single factor auhtenticated sessions as valid as well and not require multiple factors.
Bypassing second authentication factors weakens multifactor authentication and enables attackers to bypass the more secure factor. An attacker can target the TOTP code alone, only six digits, bypassing password verification entirely and potentially compromising accounts with 2FA enabled.
Affected Versions
Systems using the session API (v2 beta and v2) directly or via the new login UI in the following versions are affected:
- 4.x:
4.0.0to4.5.0(including RC versions) - 3.x:
3.0.0to3.4.2(including RC versions) - 2.x:
v2.53.6tov2.53.9,v2.54.3tov2.54.10,2.55.0to2.71.17
Patches
The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring a configured second factor regardless of the login policies requireMFA or requireMFAForLocalUsers configuration.
4.x: Upgrade to >=4.6.0 3.x: Update to >=3.4.3 2.x: Update to >=2.71.18
Workarounds
The recommended solution is to update Zitadel to a patched version.
Questions
If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)
Credits
This vulnerability was found by zentrust partners GmbH during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann. The full report will be made public after the complete review.
Is GHSA-cfjq-28r2-4jv5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/zitadel/zitadel/v2, and gives you the command that fixes it.
More advisories for github.com/zitadel/zitadel/v2
- HighCVE-2026-29192ZITADEL: Stored XSS via Default URI Redirect Leads to Account Takeover · 4 Mar 2026
- HighCVE-2026-29193ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication · 4 Mar 2026
- CriticalCVE-2026-29191ZITADEL has 1-Click Account Takeover via XSS in /saml-post Endpoint · 4 Mar 2026
- LowCVE-2026-27945ZITADEL has potential SSRF via Actions · 27 Feb 2026
- HighCVE-2025-67495ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login · 8 Dec 2025
- HighCVE-2026-29067ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login · 8 Dec 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.