CVE-2025-64101

Affected Versions

Systems running one of the following versions:

• 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.0.0 to 2.71.17

Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all Forwarded and X-Forwarded-Host header values before sending requests to ZITADEL self-hosted environments.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

Credits

Thanks to Amit Laish, GE Vernova for finding and reporting the vulnerability.

A potential vulnerability exists in ZITADEL's password reset mechanism. ZITADEL utilizes the Forwarded or X-Forwarded-Host header from incoming requests to construct the URL for the password reset confirmation link. This link, containing a secret code, is then emailed to the user.

If an attacker can manipulate these headers (e.g., via host header injection), they could cause ZITADEL to generate a password reset link pointing to a malicious domain controlled by the attacker. If the user clicks this manipulated link in the email, the secret reset code embedded in the URL can be captured by the attacker. This captured code could then be used to reset the user's password and gain unauthorized access to their account.

It's important to note that this specific attack vector is mitigated for accounts that have Multi-Factor Authentication (MFA) or Passwordless authentication enabled.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2025-64101 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.71.18, 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3); upgrading removes the vulnerable code path.

Kodem intelligence

Patched version ensure proper validation of the headers:

4.x: Upgrade to >=4.6.0
3.x: Update to >=3.4.3
2.x: Update to >=2.71.18

1. What is CVE-2025-64101? CVE-2025-64101 is a high-severity open redirect vulnerability in github.com/zitadel/zitadel/v2 (go), affecting versions >= 2.0.0, < 2.71.18. It is fixed in 2.71.18, 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2025-64101? CVE-2025-64101 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/zitadel/zitadel/v2 are affected by CVE-2025-64101? github.com/zitadel/zitadel/v2 (go) versions >= 2.0.0, < 2.71.18 is affected.
4. Is there a fix for CVE-2025-64101? Yes. CVE-2025-64101 is fixed in 2.71.18, 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3. Upgrade to this version or later.
5. Is CVE-2025-64101 exploitable, and should I be worried? Whether CVE-2025-64101 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-64101 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-64101?
   • Upgrade github.com/zitadel/zitadel/v2 to 2.71.18 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3 or later