CVE-2026-117859: Red Hat Build of Keycloak · Always-Incorrect Control Flow Implementation
Affects Red Hat Build of KeycloakSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 29 Oct 2026, 07:26 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Build of Keycloakkeycloak-services | Affected– | Fixed in– |
| Red Hat Build of Keycloakrhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat Single Sign-On 7keycloak-services | Affected– | Fixed in– |
AI-suggested
Currently, there is no available mitigation that meets Red Hat's criteria for ease of use, applicability, and stability. Red Hat Product Security indicates that mitigation options are either unavailable or insufficient. Users should monitor the Red Hat advisory for updates and consider upgrading to a fixed version once available. Until then, no specific mitigation actions are recommended.
Description
CVE-2026-117859 is a moderate severity vulnerability in the Pushed Authorization Request (PAR) implementation of the keycloak-services component in Red Hat Build of Keycloak. The flaw occurs when an authentication flow is restarted, which incorrectly clears internal markers tracking PAR consumption while leaving the request active. This allows an attacker with valid client credentials to reuse the same authorization request to obtain multiple access tokens, bypassing the intended single-use restriction.