Skip to main content
VulnerabilityPublished

CVE-2026-117859: Red Hat Build of Keycloak · Always-Incorrect Control Flow Implementation

Affects Red Hat Build of KeycloakSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 29 Oct 2026, 07:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Build of Keycloakkeycloak-servicesAffected–Fixed in–
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–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.

References

Community reviews

Loading reviews…