GHSA-9993-rfwp-rhwf: High severity go/github.com/zitadel/zitadel vulnerability

Published Sep 24, 2026
·
Updated

Summary

A vulnerability in ZITADEL’s Login V2 UI allowed a password-verified browser session to be reused for a new authentication request without re-checking a user’s enrolled second factor (TOTP, OTP, or U2F). An attacker who already knows valid credentials can fully authenticate to an application without completing MFA.

Impact

ZITADEL Login V2 issues a session as soon as the user’s password is verified, before the MFA challenge is completed. If the MFA step is abandoned (for example by navigating back) and login is started again, Login V2 may reuse that existing session instead of requiring the second factor.

Session validity checks only enforced MFA verification when the organization’s login policy had Force MFA (or Force MFA for local users only) enabled. They did not treat a voluntarily enrolled second factor as required. In the common case where MFA is available on the user but not organization-mandated, a password-only session was treated as fully authenticated and used to complete the OIDC or SAML callback, bypassing the user’s second factor.

Scope note: This issue affects customer applications that authenticate users through the hosted Login V2 UI (OIDC/SAML). It does not affect Login V1. It also does not affect authentication to ZITADEL itself — including the Console, the Management/Admin APIs, and user self-management — even when Login V2 is enabled.

Affected Versions

Systems running one of the following versions are affected:

4.x: 4.0.0 through 4.16.0 (including RC versions)

Patches

The vulnerability has been addressed in the latest releases. The patch ensures Login V2 validates that any second factor enrolled on the user has been verified before an existing session can be reused to complete authentication.

4.x: Upgrade to $\ge$ 4.16.1

Workarounds

If an immediate upgrade is not possible, enable Force MFA (or Force MFA for local users only, if you want to exempt IdP/federated logins) in the affected organization’s — or the instance default — login policy. This makes second-factor verification mandatory for password logins and closes this session-reuse bypass.

Note that this is a broader policy change (MFA becomes mandatory for the scoped local logins) rather than a narrow fix limited to users who already self-enrolled a second factor.

Questions

If you have any questions or comments about this advisory, please email us at security@zitadel.com

Credits

Thanks to Philippe Wechsler (@MadMonkey87) for finding and reporting the vulnerability.

Affected Software

1 affected componentFixes available
go/github.com/zitadel/zitadel<1.80.0-v2.20.0.20260717062356-56f4798ed31f
1.80.0-v2.20.0.20260717062356-56f4798ed31f

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/zitadel/zitadel to a version that resolves this vulnerability.

    Fixed in 1.80.0-v2.20.0.20260717062356-56f4798ed31f
  2. Upgrade

    Upgrade ZITADEL to a version that resolves this vulnerability.

    Fixed in 4.16.1
  3. Configuration

    Enable Force MFA in the affected organization’s login policy or the instance default login policy. Alternatively, enable Force MFA for local users only to exempt IdP/federated logins.

    ZITADEL Login V2 Force MFA = enabled

Event History

Sep 24, 2026
Advisory Published
via GitHub·06:19 PM
Data Sourced
via GitHub·06:19 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Customer applications that authenticate users through ZITADEL's hosted Login V2 are affected when a user has an enrolled second factor but the organization's login policy does not require MFA. The issue applies to voluntarily enrolled TOTP, OTP, or U2F factors that are not enforced by policy.

2

What does an attacker need to bypass the second factor?

The attacker must already know valid user credentials. They can use a password-verified session created before the MFA challenge is completed, abandon that challenge, and begin authentication again so the session is reused.

3

Does enabling Force MFA prevent the bypass?

Yes. Session validity checks enforced MFA verification when the organization's login policy enabled Force MFA or Force MFA for local users only. Organizations relying only on users voluntarily enrolling a second factor were not protected by those checks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203