Starting from 2.53.6, 2.54.3, and 2.55.0, 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. This vulnerability is fixed in 4.6.0, 3.4.3, and 2.71.18.
References
Configurations
Configuration 1 (hide)
|
History
04 Nov 2025, 13:17
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.8 |
| First Time |
Zitadel
Zitadel zitadel |
|
| CPE | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* | |
| References | () https://github.com/zitadel/zitadel/commit/b284f8474eed0cba531905101619e7ae7963156b - Patch | |
| References | () https://github.com/zitadel/zitadel/security/advisories/GHSA-cfjq-28r2-4jv5 - Vendor Advisory |
29 Oct 2025, 19:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-10-29 19:15
Updated : 2025-11-04 13:17
NVD link : CVE-2025-64103
Mitre link : CVE-2025-64103
CVE.ORG link : CVE-2025-64103
JSON object : View
Products Affected
zitadel
- zitadel
