Advisory

GHSA-cfjq-28r2-4jv5

Also known as: CVE-2025-64103, GO-2025-4083

Summary

Zitadel May Bypass Second Authentication Factor

Details

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.0 to 4.5.0 (including RC versions)
  • 3.x: 3.0.0 to 3.4.2 (including RC versions)
  • 2.x: v2.53.6 to v2.53.9, v2.54.3 to v2.54.10, 2.55.0 to 2.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 [[email protected]](mailto:[email protected])

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-10-29 22:21 UTC
Modified
2025-11-05 22:14 UTC

Affected packages and fixes

github.com/zitadel/zitadel/v2

Go · All systems

Affected

  • introduced 2.53.6, last affected 2.53.9 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/zitadel/zitadel/v2

Go · All systems

Affected

  • introduced 2.54.3, last affected 2.54.10 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/zitadel/zitadel/v2

Go · All systems

Affected

  • introduced 2.55.0, fixed 2.71.18 (semver)

Fixed versions

2.71.18

Fix

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 0, fixed 1.80.0-v2.20.0.20251029091250-b284f8474eed (semver)

Fixed versions

1.80.0-v2.20.0.20251029091250-b284f8474eed

Fix

  • Fixed version 1.80.0-v2.20.0.20251029091250-b284f8474eed
    go get github.com/zitadel/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences