CVE-2026-94217Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision
Updated under an hour ago ()
Does this affect you?
It affects Red Hat Build of Keycloak and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 3.5 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
- Weakness (CWE)
- CWE-862
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- redhat
- NVD analysis
- Awaiting Analysis
- Record last updated
- Sep 24, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Red Hat Red Hat Build of Keycloak redhat:build_keycloak | All versions | CNA record |
Red Hat Red Hat Single Sign-On 7 redhat:red_hat_single_sign_on | 7 | CNA record |
References
- https://access.redhat.com/security/cve/CVE-2026-94217vdb-entry, x-refsource-redhat
- https://bugzilla.redhat.com/show_bug.cgi?id=2537313issue-tracking, x-refsource-redhat
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.