CVE-2026-118947: Red Hat Build of Keycloak · Insecure Direct Object Reference
Affects Red Hat Build of KeycloakSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 30 Oct 2026, 00:59 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 30 Oct 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 29 Oct 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– |
AI-suggested
Red Hat has published an advisory for CVE-2026-118947 but does not currently list fixed versions or patches. Until a fix is available, ensure that remote resource management is configured securely and restrict the uma_protection role to trusted users only. Monitor Red Hat communications for forthcoming patches or mitigations.
Description
CVE-2026-118947 is a vulnerability in the UMA resource registration endpoint of the keycloak-services component in Red Hat Build of Keycloak. When remote resource management is enabled, an authenticated user with the uma_protection role and knowledge of a target resource ID can update resources they do not own. This allows unauthorized modification of resource configurations such as names, URIs, and scopes. Exploitation requires valid credentials and specific permissions. The vulnerability is due to a missing ownership check in the resource registration code path.