VulnerabilityPublished 27 May 2026Updated 20 Aug 2026

CVE-2026-9689: Red Hat build of Keycloak 26.4 · Improper Validation of Consistency Within Input

Affects Red Hat build of Keycloak 26.4Source CVE Database V5

Compare

Not known to be exploited · CVSS 4.2 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-1288

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat build of Keycloak 26.4	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.4	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.4.14	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.6	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.6	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.6.5	Affected–	Fixed in–

AI-suggested

Red Hat has released Keycloak 26.4.14 which includes fixes for CVE-2026-9689 among other vulnerabilities. Users should upgrade to this version to remediate the issue. Until the update is applied, mitigation involves avoiding the use of wildcard redirect URIs in client configurations and reviewing client application behavior regarding duplicate query parameters. Red Hat's advisory does not indicate that no action is required; therefore, applying the official update is recommended.

Description

A flaw was found in Keycloak, an open-source identity and access management solution. When a client application is configured to accept broad redirect Uniform Resource Identifiers (URIs), a remote attacker can manipulate the authentication process by crafting a special web address. If a user clicks this link, the client application might incorrectly prioritize attacker-controlled information over legitimate data. This vulnerability, known as HTTP parameter pollution, could allow an attacker to bypass security measures or gain unauthorized access to resources.

Impact

The impact is limited to confidentiality and integrity with low severity, as the vulnerability could allow an attacker to bypass security measures or gain unauthorized access by manipulating OIDC response parameters. There is no impact on availability. Exploitation requires user interaction and depends on the client application's handling of duplicate query parameters. No known exploits are reported in the wild.

Summary

This vulnerability arises from improper validation of consistency within input parameters in Keycloak's OIDC redirect URI handling. Specifically, when a client is configured to accept broad or wildcard redirect URIs, an attacker can exploit HTTP parameter pollution by crafting authorization URLs with duplicated response parameters. If the client application prioritizes the first occurrence of these parameters ('first-wins' strategy), it may process attacker-controlled data over legitimate data, potentially bypassing security controls or gaining unauthorized access. The vulnerability is contingent on client behavior and requires user interaction (clicking a malicious link). Red Hat's advisory references CWE-1288 and assigns a CVSS 3.1 score of 4.2 (medium severity). The vendor advisory does not explicitly state a patch for this specific CVE alone but references a Keycloak 26.4.14 update that addresses multiple vulnerabilities including CVE-2026-9689.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 13:16 UTC

Technical details

References

Community reviews

Related threats