CVE-2026-29193: ZITADEL: Bypassing Zitadel Login Behavior and Security Policy in Login V2

Published Mar 4, 2026
·
Updated

Summary

A vulnerability in Zitadel's login V2 UI allowed users to bypass login behavior and security policies and self-register new accounts or sign in using password even if corresponding options were disabled in their organizaton.

Impact

Zitadel enables administrators to configure their organization’s login behavior and security policies. As part of this functionality, they can disable user self-registration, enforce passwordless logins only, and more.

Due to improper enforcement an attacker could send direct HTTP requests to the login UI and create accounts in organizations that have disabled user self-registration, and gain unauthorized access to the system. The same attack vector could be used to authenticate for example using username and password even when this login method was disabled.

Affected Versions

Systems running one of the following versions are affected: - 4.x: 4.0.0 through 4.12.0 (including RC versions)

Patches

The vulnerability has been addressed in the latest releases. The patch resolves the issue by enforcing the policies on the logiin UI server.

4.x: Upgrade to >=4.12.1

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

Credits

ZITADEL extends thanks once again to Amit Laish from GE Vernova for finding and reporting the vulnerability.

Other sources

ZITADEL is an open source identity management platform. From version 4.0.0 to 4.12.0, a vulnerability in Zitadel's login V2 UI allowed users to bypass login behavior and security policies and self-register new accounts or sign in using password even if corresponding options were disabled in their organizaton. This issue has been patched in version 4.12.1.

— MITRE

Affected Software

3 affected componentsFixes available
go/github.com/zitadel/zitadel>=4.0.0<=4.12.0
4.12.1
go/github.com/zitadel/zitadel/v2>=4.0.0<=4.12.0
4.12.1
ZITADEL ZITADEL>=4.0.0<4.12.1

Event History

Mar 4, 2026
Advisory Published
via GitHub·10:51 PM
Data Sourced
via GitHub·10:51 PM
DescriptionSeverityWeaknessAffected Software
Mar 7, 2026
CVE Published
via MITRE·03:11 PM
Data Sourced
via MITRE·03:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 26, 58161
Event
via FIRST·06:40 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-29193?

CVE-2026-29193 is considered a critical vulnerability due to its potential to allow unauthorized account registration and login.

2

How do I fix CVE-2026-29193?

To fix CVE-2026-29193, update Zitadel to version 4.12.1 or later, which addresses this vulnerability.

3

What impact does CVE-2026-29193 have on user accounts?

CVE-2026-29193 allows users to bypass security policies, enabling unauthorized self-registration and login despite restrictions set by administrators.

4

Which versions of Zitadel are affected by CVE-2026-29193?

CVE-2026-29193 affects Zitadel versions from 4.0.0 to 4.12.0.

5

Is there a workaround for CVE-2026-29193 until I can update?

There are no known workarounds for CVE-2026-29193, so updating to the fixed version is strongly recommended.

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