Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.5
CVE-2026-94217: Keycloak SSO lets users inherit others' resource permissions
CVE-2026-94217 · published 28 days ago
Summary
The Red Hat build of Keycloak and Red Hat Single Sign‑On 7 can mix up access rights when two users create resources with the same name. When a user asks for a token, the system may wrongly combine permissions from both owners, giving the requester rights to the other person's data. Upgrade to the latest patched version and avoid using identical resource names across different accounts.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| red hat | red hat build of keycloak | All versions |
| red hat | red hat single sign-on 7 | All versions |
Original advisory text
Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision
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.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-862Missing Authorization
Timeline
Published21 Sep 2026
Updated19 Oct 2026
First seen21 Sep 2026
Track software like this
Free during beta