Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
Red Hat Red Hat Build of Keycloak
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Keycloak 的用户管理型访问（UMA，User-Managed Access）实现中发现了一个缺陷。该问题出现在授权令牌端点处理权限票据（permission tickets）的过程中。当两个不同用户拥有同名资源时，如果其中一个用户请求授权令牌，系统会错误地合并这两个资源的权限。这使得攻击者能够获取到本不应被共享的受害者资源上的访问范围（scopes）。

CVSS 3.5 · Low
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-94217

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Red Hat Red Hat Build of Keycloak - cpe:/a:redhat:build_keycloak:
Red Hat Red Hat Build of Keycloak - cpe:/a:redhat:build_keycloak:
Red Hat Red Hat Build of Keycloak - cpe:/a:redhat:build_keycloak:
Red Hat Red Hat Single Sign-On 7 - cpe:/a:redhat:red_hat_single_sign_on:7

II. Public POCs for CVE-2026-94217

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-94217

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-94217 (2)

Same Patch Batch · Red Hat · 2026-09-21 · 5 CVEs total

CVE-2026-15801 8.0 HIGH Cri-o: cri-o: insufficient validation during container checkpoint restore
CVE-2026-94215 5.5 MEDIUM Keycloak-services: keycloak-services: cross-realm client read/write via request-level cach
CVE-2026-94213 4.9 MEDIUM Keycloak-services: keycloak-services: authorization services policy evaluation endpoint le
CVE-2026-94218 3.1 LOW Keycloak-services: keycloak-services: 2fa setup enforcement bypass via authentication sess

IV. Related Vulnerabilities

Same product: Red Hat Build of Keycloak
Same vendor: Red Hat
Same weakness: CWE-862

V. Comments for CVE-2026-94217

No comments yet

Leave a comment