CVE-2026-94217
Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision
What happened?
A flaw was found in the User-Managed Access (UMA) implementation of Keycloak. The issue occurs in the authorization token endpoint when processing permission tickets. If two different users own resources with the same name, the system incorrectly merges the permissions from both resources when one user requests an authorization token. This allows an attacker to gain access scopes on a victim's resource that were never intended to be shared.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| keycloak/rhbk-openshift-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| keycloak-servicesRed Hat | Default status: unaffected | See vendor advisory |
| rhbk/keycloak-rhel9Red Hat | Default status: unaffected | See vendor advisory |
| keycloak-servicesRed Hat | Default status: unaffected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.