ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login
Published 8 Dec 2025 · Updated 9 Mar 2026
Is your project on an affected github.com/zitadel/zitadel?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.80.0-v2.20.0.20251208091519-4c879b47334e
- Fixed in
- 1.80.0-v2.20.0.20251208091519-4c879b47334e
go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251208091519-4c879b47334e- Affected
- >=1.83.4 <=1.87.5
- Fixed in
- No fix released
- Affected
- >=4.0.0-rc.1 <4.7.1
- Fixed in
- 4.7.1
go get github.com/zitadel/zitadel@v4.7.1- Affected
- <1.80.0-v2.20.0.20251208091519-4c879b47334e
- Fixed in
- 1.80.0-v2.20.0.20251208091519-4c879b47334e
go get github.com/zitadel/zitadel/v2@v1.80.0-v2.20.0.20251208091519-4c879b47334eDetails
Summary
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.
Impact
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.
Affected Versions
Systems using the login UI (v2) and running one of the following versions are affected:
- v4.x:
4.0.0-rc.1through4.7.0
Patches
The 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:
- the
ZITADEL_API_URLis set and is pointing to your instance, resp. system in multi-instance deployments. - the HTTP
host(or ax-forwarded-host) is passed in your reverse proxy to the login UI. - a
x-zitadel-instance-host(orx-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:
- 4.x: Upgrade to >=4.7.1
Workarounds
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.
Questions
If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)
Credits
Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
Is GHSA-pfrf-9r5f-73f5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/zitadel/zitadel, and gives you the command that fixes it.
More advisories for github.com/zitadel/zitadel
- LowCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 in github.com/zitadel/zitadel · 1 Oct 2026
- LowCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() in github.com/zitadel/zitadel · 1 Oct 2026
- HighCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 · 24 Sept 2026
- HighCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() · 24 Sept 2026
- LowCVE-2026-56665ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider in github.com/zitadel/zitadel · 16 Sept 2026
- LowCVE-2026-56666ZITADEL: Auto-linking by email: IdP-side email verification is not checked in github.com/zitadel/zitadel · 16 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.