Skip to main content
VulnerabilityPublished Updated

CVE-2026-93999: Red Hat Build of Keycloak · Missing Authorization

Affects Red Hat Build of KeycloakSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.2 Medium.

Data as of 3 Nov 2026, 10:58 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Build of KeycloakAffected–Fixed in–
Red HatRed Hat Single Sign-On 7Affected–Fixed in–

AI-suggested

According to the Red Hat advisory, no mitigation is currently available that meets their criteria for ease of use, applicability, or stability. Users should monitor the Red Hat advisory for updates and consider compensating controls where feasible. Red Hat Product Security continues to evaluate the issue and may provide fixes or mitigations in the future.

Description

A flaw was found in the OIDC protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs during the token refresh process when the server restores requested audiences from stored client IDs. Keycloak fails to verify if the target audience client is still enabled before issuing a new access token. This allows an application with an existing refresh token to continue obtaining valid access tokens for a disabled client, potentially bypassing administrative access controls for resource servers that rely on offline JWT validation.

References

Community reviews

Loading reviews…