CVE-2026-94217

Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision

  • Low 3.5

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.

Key facts

Published
21 Sep 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.293% likely to be exploited in the next 30 days, higher than 22.137% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 3.5CVSS 3.1, Lowfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: unaffected

Timeline

  1. 19 Sep 2026 Reported to Red Hat.
  2. 19 Sep 2026 Made public.
  3. 21 Sep 2026 Published

Weakness

References