ZITADEL is missing enforcement of organization scopes

Summary

ZITADEL is an open source identity management platform. Versions prior to 3.4.9 and 4.0.0 through 4.12.2 allowed users to bypass organization enforcement during authentication. Zitadel allows applications to enforce an organzation context during authentication using scopes (urn:zitadel:iam:org:id:{id} and urn:zitadel:iam:org:domain:primary:{domainname}). If enforced, a user needs to be part of the required organization to sign in. While this was properly enforced for OAuth2/OIDC authorization requests in login V1, corresponding controls were missing for device authorization requests and all login V2 and OIDC API V2 endpoints. This allowed users to bypass the restriction and sign in with users from other organizations. Note that this enforcement allows for an additional check during authentication and applications relying on authorizations / roles assignments are not affected by this bypass. This issue has been patched in versions 3.4.9 and 4.12.3.

Timeline

1. Mar 20, 2026, 10:21 AM UTCCVE published
2. Mar 20, 2026, 7:30 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Mar 20, 2026, 7:31 PM UTCRecord last updated

Affected versions

• zitadel zitadel

  From 4.0.0-rc.1 · fixed in 4.12.3; From 3.0.0-rc.1 · fixed in 3.4.9; fixed in 1.80.0-v2.20.0.20260317120401-d90285929ca0

• github.com/zitadel/zitadelGo

  fixed in 1.80.0-v2.20.0.20260317120401-d90285929ca0

• github.com/zitadel/zitadelGo

  From 4.0.0-rc.1 · fixed in 4.12.3

• github.com/zitadel/zitadelGo

  From 3.0.0-rc.1 · fixed in 3.4.9

References 4