Servers and applications
GHSA-qqv8-37gw-ww2q
Missing second-factor check on authenticator enrollment in Login V2 (MFA bypass)
- Severity
- High 8.1
- Published
- 18 Nov 2026
- Last changed
- 19 Nov 2026
- Added to UpHeron
- 18 Nov 2026
- Fixed in
- 4.20.5
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N- Sources
- Project advisories (GitHub)
Description
ZITADEL’s hosted Login V2 UI allowed an attacker who knows a user’s first factor — typically the password — to add a new authenticator to that user’s account without completing the second factor the user had already enrolled. A newly registered passkey satisfies multi-factor authentication on its own, so the attacker could then sign in with it and was never asked for the victim’s TOTP, OTP-SMS, OTP-Email or U2F factor.
Login V2 accepted authenticator enrollment as soon as the session had a verified first factor, without checking whether the second factor already enrolled on the account had been verified in that session.
An attacker who knows a user’s password (or can sign in as the user at a linked external identity provider) can:
- Bypass the user’s enrolled second factor (TOTP, OTP-SMS, OTP-Email or U2F) by adding an authenticator of their own — a passkey, or another second factor they then choose at sign-in — and sign in to applications as that user.
Workarounds
The recommended solution is to upgrade to a patched version. There is no configuration that fully closes this gap on unpatched versions; enabling Force MFA or disallowing passkeys in the login policy does not mitigate it.
After upgrading, administrators may want to review authenticators (passkeys, second factors and identity provider links) recently added to accounts and remove any the user does not recognize.
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-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
- GHSA-9vfg-mj6p-vwjcLogin V2: opening a link adds an OTP email or SMS second factor to a signed-in user without confirmationMedium 4.3 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-qqv8-37gw-ww2q
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-qqv8-37gw-ww2q