CVE-2026-29193 — zitadel
HIGHCVE-2026-29193 is a high-severity (CVSS 8.2) Improper Authentication vulnerability in github.com/zitadel/zitadel/v2. A fix is available for github.com/zitadel/zitadel/v2 — see the affected versions and patch details below.
ZITADEL: Bypassing Zitadel Login Behavior and Security Policy in Login V2
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-29193.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.0through4.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 [email protected]
Credits
ZITADEL extends thanks once again to Amit Laish from GE Vernova for finding and reporting the vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 4.0.0&&< 4.12.1 | 4.12.1go get github.com/zitadel/zitadel/v2@v4.12.1 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 4.0.0&&< 4.12.1 | 4.12.1go get github.com/zitadel/zitadel@v4.12.1 |
Affected Products
zitadelzitadelDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel/v2 to 4.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29193 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-29193 in your dependencies?
Find it across Go, including transitive dependencies.