ZITADEL: Stored XSS via Default URI Redirect Leads to Account Takeover
Published 4 Mar 2026 · Updated 23 Mar 2026
Is your project on an affected github.com/zitadel/zitadel/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.0.0 <4.12.0
- Fixed in
- 4.12.0
go get github.com/zitadel/zitadel/v2@v4.12.0- Affected
- >=4.0.0 <4.12.0
- Fixed in
- 4.12.0
go get github.com/zitadel/zitadel@v4.12.0Details
Summary
A vulnerability in Zitadel's login V2 interface was discovered, allowing for possible account takeover.
Impact
Zitadel allows organization administrators to change the default redirect URI for their organization. This setting enables them to redirect users to an arbitrary location after they log in.
Due to missing restrictions and improper handling, malicious javascrtipt code could be executed in Zitadel login UI (v2) using the users’ browser.
An unauthenticated remote attacker can exploit this Stored XSS vulnerability, reset the password of their victims, and take over their accounts.
It's important to note that this specific attack vector is mitigated for accounts that have Multi-Factor Authentication (MFA) or Passwordless authentication enabled.Stored XSS vulnerability.
Affected Versions
Systems running one of the following versions are affected:
- 4.x:
4.0.0through4.11.1(including RC versions)
Patches
The vulnerability has been addressed in the latest releases. The login UI prevents execution of such code. Additionally, the page to change the password, now always requires the user's current password regardless of the state of the authenticated session.
4.x: Upgrade to >= 4.12.0
Workarounds
The recommended solution is to upgrade to a patched version.
Questions
If there are any questions or comments about this advisory, please send an email to [security@zitadel.com](mailto:security@zitadel.com)
Credits
ZITADEL extends thanks once again to Amit Laish from GE Vernova for finding and reporting the vulnerability.
Is GHSA-6rx5-m2rc-hmf7 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/v2, and gives you the command that fixes it.
More advisories for github.com/zitadel/zitadel/v2
- HighCVE-2026-29193ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication · 4 Mar 2026
- CriticalCVE-2026-29191ZITADEL has 1-Click Account Takeover via XSS in /saml-post Endpoint · 4 Mar 2026
- LowCVE-2026-27945ZITADEL has potential SSRF via Actions · 27 Feb 2026
- HighCVE-2025-67495ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login · 8 Dec 2025
- HighCVE-2026-29067ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login · 8 Dec 2025
- CriticalCVE-2025-67494ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login · 8 Dec 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.