# CVE-2026-33132: ZITADEL is missing enforcement of organization scopes > Attackers can bypass organization scope enforcement during device or API authentication, allowing sign-in from unauthorized organizations. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** GHSA-g2pf-ww5m-2r9m, GO-2026-4751 ## What is CVE-2026-33132? CVE-2026-33132 is a medium-severity authentication bypass vulnerability in zitadel, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-33132? 7 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260317120401-d90285929ca0 | | `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260317120401-d90285929ca0 | | `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260317120401-d90285929ca0 | | `github.com/zitadel/zitadel` | Go | From 3.0.0-rc.1 | 3.4.9 | | `github.com/zitadel/zitadel` | Go | From 3.0.0-rc.1 | 3.4.9 | | `github.com/zitadel/zitadel` | Go | From 4.0.0-rc.1 | 4.12.3 | | `github.com/zitadel/zitadel` | Go | From 4.0.0-rc.1 | 4.12.3 | Products: Zitadel Zitadel. ## How do I fix CVE-2026-33132? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 1.80.0-v2.20.0.20260317120401-d90285929ca0, 3.4.9 or 4.12.3. ## Is CVE-2026-33132 being exploited? There is no known exploitation of CVE-2026-33132 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33132 and fix it if it is affected. What it is: CVE-2026-33132 is a medium-severity authentication bypass vulnerability in zitadel, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-33132 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260317120401-d90285929ca0 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260317120401-d90285929ca0 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260317120401-d90285929ca0 - github.com/zitadel/zitadel (Go): affected from 3.0.0-rc.1; fixed in 3.4.9 - github.com/zitadel/zitadel (Go): affected from 3.0.0-rc.1; fixed in 3.4.9 - github.com/zitadel/zitadel (Go): affected from 4.0.0-rc.1; fixed in 4.12.3 - github.com/zitadel/zitadel (Go): affected from 4.0.0-rc.1; fixed in 4.12.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33132/ (Markdown: https://insights.sbomify.com/CVE-2026-33132/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33132 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33132 - OSV: https://osv.dev/vulnerability/CVE-2026-33132 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33132/ Summaries are generated and may contain mistakes; the official description above is the record.