CVE-2026-29193: ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication

CVE-2026-29193 · Severity: low · CVSS 3.1 · Published 2026-03-10

ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication in github.com/zitadel/zitadel

Technologies: github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2026-29193 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-29193 being exploited in the wild.
How severe is CVE-2026-29193?
Low severity, with a CVSS score of 3.1, published 10 March 2026.
Which products and versions are affected?
github.com/zitadel/zitadel (Go) SEMVER:introduced=0, SEMVER:introduced=4.0.0,fixed=4.12.1; github.com/zitadel/zitadel/v2 (Go) SEMVER:introduced=4.0.0,fixed=4.12.1.
Is there a fix for CVE-2026-29193?
Yes. github.com/zitadel/zitadel (Go): upgrade to 4.12.1 or later; github.com/zitadel/zitadel/v2 (Go): upgrade to 4.12.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-29193?
Check whether you run github.com/zitadel/zitadel (Go) or github.com/zitadel/zitadel/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/zitadel/zitadel (Go): upgrade to 4.12.1 or later
    go get github.com/zitadel/zitadel@v4.12.1
  • github.com/zitadel/zitadel/v2 (Go): upgrade to 4.12.1 or later
    go get github.com/zitadel/zitadel/v2@v4.12.1

Affected products

  • github.com/zitadel/zitadel (Go) SEMVER:introduced=0, SEMVER:introduced=4.0.0,fixed=4.12.1
  • github.com/zitadel/zitadel/v2 (Go) SEMVER:introduced=4.0.0,fixed=4.12.1

Identifiers

  • CVE-2026-29193
  • GHSA-25rw-g6ff-fmg8
  • GO-2026-4604

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.