CVE-2026-133226: Red Hat Build of Keycloak · Incorrect Privilege Assignment
Affects Red Hat Build of KeycloakSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 20 Nov 2026, 02:05 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 4.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Build of Keycloakkeycloak-services | Affected– | Fixed in– |
| Red Hat Build of Keycloakrhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat Single Sign-On 7keycloak-services | Affected– | Fixed in– |
| Red Hat Single Sign-On 7rh-sso7-keycloak | Affected– | Fixed in– |
AI-suggested
Red Hat currently does not provide a mitigation or patch that meets their criteria for ease of use, applicability, or stability. Users should monitor Red Hat's advisory for updates. Since the vulnerability is limited to the user's own resources, no immediate urgent action is mandated by Red Hat.
Description
CVE-2026-133226 is a vulnerability in Red Hat's build of Keycloak where the Account API endpoint for sharing resources does not properly verify if owner-managed access is enabled and improperly accepts permission scopes not assigned to the resource. This allows an authenticated user to generate pre-granted permission tickets, bypassing policy evaluation and obtaining access tokens with unauthorized scopes. The vulnerability is limited to resources owned by the authenticated user, preventing unauthorized access to other users' data. Red Hat rates this issue as low severity for their products due to the limited blast radius and lack of cross-tenant impact. No official fix or mitigation currently meets Red Hat's criteria for deployment.