Skip to main content
VulnerabilityPublished Updated

CVE-2026-93999: Missing Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-93999· Medium 4.2

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

Data as of 6 Nov 2026, 14:05 UTC

CVSS 3.1 base score
4.2Medium
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.14.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 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 published a security advisory (RHSA-2026:95761) with updates to Keycloak 26.6.8 addressing multiple security issues. However, the advisory does not explicitly confirm a fix for CVE-2026-93999. No alternative mitigations or workarounds are specified in the advisory.

Description

A vulnerability in the OpenID Connect (OIDC) protocol implementation of Keycloak allows an application holding a valid refresh token to obtain new access tokens for a client that has been disabled. This occurs because Keycloak does not verify whether the target audience client is still enabled during the token refresh process. This flaw can potentially bypass administrative access controls for resource servers relying on offline JWT validation.

References

Community reviews

Loading reviews…