Skip to main content
VulnerabilityPublished Updated

CVE-2026-94217: Missing Authorization

Source GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-94217· Low 3.5

Not known to be exploited · CVSS 3.5 Low : update Red Hat build of Keycloak 26.6.8 when convenient.

Data as of 6 Nov 2026, 14:04 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.13.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat build of Keycloak 26.6.8keycloak/rhbk-openshift-rhel9Affected–Fixed in–
Red Hat build of Keycloak 26.6.8keycloak-servicesAffected–Fixed in–
Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–Fixed in–

AI-suggested

Red Hat has released an official security update in the Red Hat build of Keycloak version 26.6.8 that addresses this vulnerability along with other security issues. Users should upgrade to Keycloak 26.6.8 or later to remediate this flaw. No additional mitigation steps are indicated in the vendor advisory.

Description

A vulnerability in the User-Managed Access (UMA) implementation of Keycloak allows an attacker to gain unauthorized access scopes on a victim's resource. This occurs when two different users own resources with the same name, and the authorization token endpoint incorrectly merges permissions from both resources during token processing.

References

Community reviews

Loading reviews…