Keycloak · CWE-358
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 20 Nov 2026, 04:36 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
Currently, no mitigation or patch meeting Red Hat's criteria for ease of use, deployment, applicability, or stability is available. Users should rely on downstream services enforcing online token introspection or client status verification to minimize impact. Monitor Red Hat advisories for updates or fixes. No urgent action is required beyond existing access control policies.
Description
A vulnerability in Keycloak's handling of User-Managed Access (UMA) token requests allows an authenticated user to obtain valid Requesting Party Tokens (RPTs) for clients or resource servers that have been administratively disabled. This occurs because Keycloak does not verify whether the target client or resource server is enabled before issuing tokens. The flaw enables bypassing of administrative access controls and permission restrictions, but does not grant privileges beyond those already authorized for the user. The impact is limited in typical deployments where downstream services enforce online token introspection or verify client status.