# ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication

Advisory record · `GHSA-25rw-g6ff-fmg8`

- **Identifiers:** `GHSA-25rw-g6ff-fmg8` · `CVE-2026-29193` · `GO-2026-4604`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 4 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Mar 2026, 22:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/zitadel/zitadel/v2` (Go): affected `>=4.0.0, <4.12.1`; fixed in `4.12.1`
- `github.com/zitadel/zitadel` (Go): affected `>=4.0.0, <4.12.1`; fixed in `4.12.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Zitadel's Login V2 UI, in the Go packages github.com/zitadel/zitadel/v2 and github.com/zitadel/zitadel, versions 4.0.0 through 4.12.0 (including release candidates), fails to enforce organization login and security policies. An attacker who can send direct HTTP requests to the login UI can self-register accounts in organizations that disabled self-registration, and sign in with a password where that method was disabled. Upgrade to version 4.12.1 or later. The source lists no workaround other than upgrading.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-25rw-g6ff-fmg8)

## Sources

- [GitHub Advisory Database: GHSA-25rw-g6ff-fmg8](https://github.com/advisories/GHSA-25rw-g6ff-fmg8)
- [OSV: GHSA-25rw-g6ff-fmg8](https://osv.dev/vulnerability/GHSA-25rw-g6ff-fmg8)
- <https://github.com/zitadel/zitadel/security/advisories/GHSA-25rw-g6ff-fmg8>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-29193>
- <https://github.com/zitadel/zitadel>
- <https://github.com/zitadel/zitadel/releases/tag/v4.12.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-25rw-g6ff-fmg8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-25rw-g6ff-fmg8/>. Everything for agents: <https://agentprime.io/llms.txt>.
