A flaw was found in Keycloak. An authenticated user with existing organization membership can exploit this flaw by accessing user-facing APIs, such as the account API or by requesting an OpenID Connect (OIDC) token with the 'organization' scope. This allows organization metadata to be disclosed in tokens, even after an administrator has explicitly disabled the Organizations feature, potentially leading to incorrect authorization decisions by resource servers.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://access.redhat.com/security/cve/CVE-2026-9791 Mitigation, Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2482458 Issue Tracking, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 4.3 · redhatNVD modified 2026-10-26 12:10
Affected (CPE criteria) 1
cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*
References 6
- https://access.redhat.com/errata/RHSA-2026:25097
- https://access.redhat.com/errata/RHSA-2026:25098
- https://access.redhat.com/errata/RHSA-2026:30049
- https://access.redhat.com/errata/RHSA-2026:30050
- https://access.redhat.com/security/cve/CVE-2026-9791 Mitigation, Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2482458 Issue Tracking, Vendor Advisory