CVE-2025-64102: Zitadel allows brute-forcing authentication factors
Summary A vulnerability in Zitadel allowed brute-force attack on OTP, TOTP and password allowing to impersonate the attacked user. Impact An attacker can perform an online brute-force attack on OTP, TOTP, and passwords. While Zitadel allows preventing online brute force attacks in scenarios like TOTP, Email OTP, or passwords using a lockout mechanism.
Published Oct 29, 2025 · Updated Nov 5, 2025
Affected packages
github.com/zitadel/zitadel/v2
- Ecosystem
- Go
- Affected
- < 2.71.18
- Fixed in
- 2.71.18
- Check
go list -m github.com/zitadel/zitadel/v2
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- < 1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8
- Fixed in
- 1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8
- Check
go list -m github.com/zitadel/zitadel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A vulnerability in Zitadel allowed brute-force attack on OTP, TOTP and password allowing to impersonate the attacked user.
Impact
An attacker can perform an online brute-force attack on OTP, TOTP, and passwords. While Zitadel allows preventing online brute force attacks in scenarios like TOTP, Email OTP, or passwords using a lockout mechanism. The mechanism is not enabled by default and can cause a denial of service for the corresponding user if enabled. Additionally, the mitigation strategies were not fully implemented in the more recent resource-based APIs.
Affected Versions
All versions within the following ranges, including release candidates (RCs), are affected:
- 4.x:
4.0.0to4.4.0(including RC versions) - 3.x:
3.0.0to3.4.2(including RC versions) - 2.x:
v2.0.0to2.71.17
Patches
The vulnerability has been addressed in the latest releases. The patch resolves the issue by enforcing the lockout policy on all OTP, TOTP and password checks. Additionally a “tar pit” has been introduced to slow down brute-force attacks by default. Zitadel responses will be delayed by t seconds, where t increases over the number of failed attempts within a given timeframe.
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.
The problem might be mitigated by enabling the optional logout policy ("Password maximum attempts") or by implementing more strict rate limits.
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.
Credited to livio-a, IAM-marco, evilgensec.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85056
ZITADEL: MFA bypass via session reuse in Login V2
high8.2Sep 24, 2026CVE-2026-85057
ZITADEL: Actions V1 sandbox escape: host file read via require()
high8.7Sep 24, 2026CVE-2026-56668
ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange
high8.1Sep 14, 2026CVE-2026-76081
ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions
medium5.5Sep 14, 2026CVE-2026-56665
ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
medium4.2Sep 11, 2026CVE-2026-56666
ZITADEL: Auto-linking by email: IdP-side email verification is not checked
medium4.8Sep 11, 2026
