Skip to content
Fencer Vulns
medium 4.3

CVE-2026-118947 json

Keycloak-services: keycloak-services: authorization bypass via uma resource registration idor

published 2026-10-30 10 d ago modified 2026-11-04 5 d ago also EUVD-2026-113442

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

A flaw was found in the UMA resource registration endpoint of the keycloak-services component, which provides the core logic for Keycloak's authorization and identity services. The issue occurs when remote resource management is enabled, allowing an authenticated user with specific permissions to update resources they do not own by providing a target resource ID in a request. This can lead to unauthorized modification of resource configurations, such as names, URIs, and scopes.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-118947 updated cvss 4.3

keycloak-services: keycloak-services: Authorization bypass via UMA resource registration IDOR

  • Red Hat Build of Keycloak rhbk/keycloak-rhel9, keycloak-services 26.6.7.redhat-00003
    affected: no fix available
  • Red Hat Single Sign-On 7 keycloak-services 26.6.7.redhat-00003
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5 d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected products

  • Red Hat Red Hat Build of Keycloak
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.