Servers and applications
GHSA-4hgj-wm6c-q7p2
Unauthenticated attacker can rename any user (including admins) through the login V1
- Severity
- High 8.2
- Published
- 24 Sept 2026
- Last changed
- 24 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.19.1
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L- Sources
- Project advisories (GitHub)
Description
ZITADEL’s hosted Login V1 UI allowed an unauthenticated attacker who knows only a victim’s login name to permanently change that account’s username. By starting an ordinary login flow, submitting the victim’s login name to identify the account, and then posting a new username, the attacker could rename any active human user on the instance — including administrators — without ever supplying a password or any second factor.
The change-username request acted on the account bound to the login flow as soon as a login name had been entered, before the flow had reached the change-username step and before any authentication factor had been verified.
An attacker with only network access to the hosted Login V1 UI and knowledge of a victim’s login name can:
- Rename any active human account on the instance, across every organization, including instance administrators - Lock the victim out of their account, because the identifier they previously logged in with no longer resolves to them -…
Workarounds
The recommended solution is to upgrade to a patched version. There is no configuration that fully closes this gap on unpatched versions.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-4hgj-wm6c-q7p2
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-4hgj-wm6c-q7p2