Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-94217

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

Products / packages Red Hat build of Keycloak 26.6.8 · Red Hat Single Sign-On 7

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:55:31 UTC
redhat · CVSS:3.1 · 3.5
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Severity

low3.5

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

A flaw in Keycloak's UMA implementation allows an attacker to gain unintended access scopes on a victim's resource when two users own resources with the same name. The issue occurs when processing permission tickets at the authorization token endpoint. The affected versions are not specified.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Red Hat · redhat

Red Hat build of Keycloak 26.6.8

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:build_keycloak:26.6::el9

Red Hat · redhat

Red Hat build of Keycloak 26.6.8

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:build_keycloak:26.6::el9

Red Hat · redhat

Red Hat build of Keycloak 26.6.8

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:build_keycloak:26.6::el9

Red Hat · redhat

Red Hat Single Sign-On 7

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:red_hat_single_sign_on:7
Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

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.

redhat guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

3 sources
access.redhat.com/errata/RHSA-2026:95761
Vendor advisoryredhat
access.redhat.com/security/cve/CVE-2026-94217
Security advisoryredhat
bugzilla.redhat.com/show_bug.cgi
Source referenceredhat

Inside the record

Evidence available

Package identity · not supplied
Version evidence · not supplied
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-94217

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-862 ↗

Missing Authorization

redhat

Related →
Contributing organizations · 2
redhat

Assigning organization

2026-11-06
CISA-ADP

Additional data publisher

2026-09-24

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.