ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication
CVE-2026-29193GHSA-25rw-g6ff-fmg8
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel 4.12.1; github.com/zitadel/zitadel/v2 4.12.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 4.0.0, <= 4.12.0
- Fixed in
- 4.12.1
Go github.com/zitadel/zitadel/v2
- Affected
- >= 4.0.0, <= 4.12.0
- Fixed in
- 4.12.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-25rw-g6ff-fmg8 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=4.0.0 =4.0.0 <=4.12.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- EPSS
- CVE-2026-29193: 0.35% estimated exploitation activity in the next 30 days; percentile 28.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-25rw-g6ff-fmg8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-29193 Advisory: ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication IDs: CVE-2026-29193, GHSA-25rw-g6ff-fmg8 Record: https://patchnext.com/advisories/cve-2026-29193 (revision 1, source checked 26 Oct 2026, 15:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.2) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 4.12.1; github.com/zitadel/zitadel/v2 4.12.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/zitadel/zitadel: affected >= 4.0.0, <= 4.12.0; fixed in 4.12.1 - Go github.com/zitadel/zitadel/v2: affected >= 4.0.0, <= 4.12.0; fixed in 4.12.1 ## Suggested inspection (read-only) - Go github.com/zitadel/zitadel: check the installed version with your package manager. - Go github.com/zitadel/zitadel/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-25rw-g6ff-fmg8 (GitHub-reviewed advisory GHSA-25rw-g6ff-fmg8 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=4.0.0 =4.0.0 <=4.12.0) Commands are suggestions: review each one before running it.
Loading voting…