https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T07:20:28.176980+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-276751 EUVD-2026-276751 2026-10-07T07:20:28.241487+00:00 EUVD-2026-276751 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33132 fkie_cve-2026-33132 2026-10-07T07:20:28.241531+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-g2pf-ww5m-2r9m GHSA-g2pf-ww5m-2r9m — Zitadel is missing enforcement of organization scopes 2026-10-07T07:20:28.241571+00:00

Affected: Go: github.com/zitadel/zitadel

### Summary

A vulnerability in Zitadel's OAuth2/OIDC interface, which allowed users to bypass organization enforcement during authentication.

### Impact

Zitadel allows applications to enforce an organzation context during authentication using [scopes](https://zitadel.com/docs/apis/openidoauth/scopes#reserved-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.

### Affected Versions

Systems running one of the following versions are affected: - **4.x**: `4.0.0` through `4.12.2` (including RC versions) - **3.x**: `3.0.0` through `3.4.8` (including RC versions)

### Patches

The vulnerability has been addressed in the latest releases. The patch resolves the issue by validating the provided scopes and enforcing the organization existence when processing the authorization request. Additionally it will prevent the use of a session of a user which does not belong to the required organization on the…