VulnerabilityPublished 6 Nov 2026

CVE-2026-97367: Red Hat Build of Keycloak · Improper Authentication

Affects Red Hat Build of KeycloakSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 6 Nov 2026, 06:20 UTC

CVSS 3.1 base score

6.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.1	6.4

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 6 Nov 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 5 Nov 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.

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, no mitigation or patch is available that meets Red Hat's criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for updates. Customers with Technical Account Managers can seek direct guidance. Until a fix is released, restricting client registration privileges and monitoring for suspicious activity may reduce risk but are not official mitigations.

Description

CVE-2026-97367 is a vulnerability in the Red Hat Build of Keycloak's Account REST API where improper session identification handling allows a malicious client with registration privileges to manipulate security tokens to hijack another user's session. This can lead to unauthorized access and modification of the victim's account, including changing recovery email and resetting the password, potentially resulting in full account takeover. Exploitation requires specific session timing, user interaction, and attacker possession of client registration privileges. No effective mitigation or patch currently meets Red Hat's criteria for deployment.

Impact

Successful exploitation allows an attacker with client registration privileges to read and modify victim account information, including changing recovery email and resetting passwords, potentially leading to full account takeover. The vulnerability impacts confidentiality and integrity but does not affect availability. Exploitation complexity is high, requiring user interaction and specific session timing.

Summary

The vulnerability in Red Hat Build of Keycloak arises from improper authentication due to lack of validation between the token subject and the resolved session user in the Account REST API. A malicious client owner can manipulate their security tokens to point to a different user's active session, enabling unauthorized access and modification of the victim's account data. The root cause involves the ability to substitute sensitive claims such as 'sid' via Dynamic Client Registration (DCR). Red Hat assesses the severity as moderate due to the complexity of exploitation and required privileges.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 06:20 UTC

Technical details

References

Community reviews

Related threats