Zitadel allows brute-forcing authentication factors

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-64102: 0.37% estimated exploitation activity in the next 30 days; percentile 30.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.0 to 4.4.0 (including RC versions) - 3.x: 3.0.0 to 3.4.2 (including RC versions) - 2.x: v2.0.0 to 2.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…

Published by the source

29 Oct 2025, 22:21 UTC

Last modified by the source

5 Nov 2025, 22:13 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xrw9-r35x-x878

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64102

Advisory: Zitadel allows brute-forcing authentication factors
IDs: CVE-2025-64102, GHSA-xrw9-r35x-x878
Record: https://patchnext.com/advisories/cve-2025-64102 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8; github.com/zitadel/zitadel/v2 2.71.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected < 1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8; fixed in 1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8
- Go github.com/zitadel/zitadel/v2: affected < 2.71.18; fixed in 2.71.18

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.
- Go github.com/zitadel/zitadel/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xrw9-r35x-x878 (GitHub-reviewed advisory GHSA-xrw9-r35x-x878 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=0 =0 <1.80.0-v2.20.0.20251029090735-b8db8cdf9cc8)

Commands are suggestions: review each one before running it.