Skip to main content
VulnerabilityPublished Updated

CVE-2025-64103: V2 · Zitadel May Bypass Second Authentication Factor

Affects github.com/zitadel/zitadel/v2Source GCVE Database

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2.71.18 soon.

Data as of 4 Nov 2026, 18:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade github.com/zitadel/zitadel/v2 to 2.71.18; github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251029091250-b284f8474eed.

Affected software

ProductAffectedFixed in
Gogithub.com/zitadel/zitadel/v2Affected
  • >=2.53.6 <=2.53.9
Fixed in–
Gogithub.com/zitadel/zitadel/v2Affected
  • >=2.54.3 <=2.54.10
Fixed in–
Gogithub.com/zitadel/zitadel/v2Affected
  • >=2.55.0 <2.71.18
Fixed in
  • 2.71.18
Gogithub.com/zitadel/zitadelAffected
  • <1.80.0-v2.20.0.20251029091250-b284f8474eed
Fixed in
  • 1.80.0-v2.20.0.20251029091250-b284f8474eed

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and users should upgrade Zitadel to versions 4.6.0 or later for the 4.x branch, 3.4.3 or later for the 3.x branch, and 2.71.18 or later for the 2.x branch. The patch enforces the requirement of a configured second factor regardless of login policy settings. No other workarounds are recommended; updating to a patched version is the advised remediation.

Description

A vulnerability in Zitadel's token verification allowed sessions to be marked as authenticated after only one factor was verified, bypassing the intended second authentication factor. This affects Zitadel versions 4.0.0 to 4.5.0, 3.0.0 to 3.4.2, and several 2.x versions up to but not including 2.71.18. The flaw weakens multifactor authentication by permitting attackers to bypass password verification and authenticate using only the TOTP code. The issue has been fixed in Zitadel versions 4.6.0, 3.4.3, and 2.71.18 and later. Users are advised to upgrade to these patched versions to mitigate the risk.

References

Community reviews

Loading reviews…