| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/zitadel/zitadel | ≥ 1.83.4, ≤ 1.87.5≥ 1.83.4≥ 4.0.0-rc.1, < 4.7.1< 1.80.0-v2.20.0.20251208091519-4c879b47334e | 4.7.11.80.0-v2.20.0.20251208091519-4c879b47334e |
| github.com/zitadel/zitadel/v2 | < 1.80.0-v2.20.0.20251208091519-4c879b47334e | 1.80.0-v2.20.0.20251208091519-4c879b47334e |
| zitadel | ≥ 4.0.0, < 4.7.1 | 4.7.1 |
A potential vulnerability exists in ZITADEL's password reset mechanism in login V2. 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.
Systems using the login UI (v2) and running one of the following versions are affected:
4.0.0-rc.1 through 4.7.0The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the X-Forwarded-Host and Forwarded headers against the instance custom and trusted domains.
Before you upgrade, ensure that:
ZITADEL_API_URL is set and is pointing to your instance, resp. system in multi-instance deployments.host (or a x-forwarded-host) is passed in your reverse proxy to the login UI.x-zitadel-instance-host (or x-zitadel-forward-host) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.Patched versions:
The recommended solution is to update ZITADEL to a patched version.
A ZITADEL fronting proxy can be configured to delete all forwarded header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.
If you have any questions or comments about this advisory, please email us at [email protected]
Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free