CVE-2025-64103
BaseFortify
Publication date: 2025-10-29
Last updated on: 2025-11-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zitadel | zitadel | From 2.53.6 (inc) to 2.53.9 (inc) |
| zitadel | zitadel | From 2.54.3 (inc) to 2.54.10 (inc) |
| zitadel | zitadel | From 2.55.0 (inc) to 2.71.18 (exc) |
| zitadel | zitadel | From 3.0.0 (inc) to 3.4.3 (exc) |
| zitadel | zitadel | From 4.0.0 (inc) to 4.6.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-308 | The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor. |
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in Zitadel versions starting from 2.53.6, 2.54.3, and 2.55.0, where multi-factor authentication (MFA) was only enforced if the login policy explicitly required it via requireMFA or requireMFAForLocalUsers settings. If a user had set up MFA but the policy did not require it, Zitadel would accept single-factor authenticated sessions as valid, effectively bypassing the second authentication factor. An attacker could exploit this by targeting only the TOTP code (a six-digit code) and bypass password verification entirely, potentially compromising accounts that had 2FA enabled. This flaw weakens the security provided by MFA. The issue was fixed in versions 4.6.0, 3.4.3, and 2.71.18.
How can this vulnerability impact me? :
This vulnerability can allow attackers to bypass the second factor of authentication in Zitadel, compromising accounts that have two-factor authentication enabled. By exploiting this flaw, attackers can gain unauthorized access by only using the TOTP code without needing the password, which significantly reduces the security of user accounts and increases the risk of account takeover.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately upgrade Zitadel to version 4.6.0, 3.4.3, or 2.71.18 or later, where the issue is fixed. Additionally, review your login policies to ensure that multi-factor authentication is properly required by enabling requireMFA or requireMFAForLocalUsers settings to enforce MFA for all applicable users.