VulnerabilityPublished 10 Nov 2026

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

Affects Red Hat Build of KeycloakSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 10 Nov 2026, 07:50 UTC

CVSS 3.1 base score

6.8Medium

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.8

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
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: 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: 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 10 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 9 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–
Red Hat Single Sign-On 7rh-sso7-keycloak	Affected–	Fixed in–

AI-suggested

Currently, Red Hat states that no mitigation is available or that existing options do not meet their criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat's advisory for updates and consider compensating controls where possible.

Description

CVE-2026-125652 is a vulnerability in the keycloak-services component of Red Hat Build of Keycloak. It occurs when a user initiates a login after visiting the password reset page, causing the system to skip mandatory Proof Key for Code Exchange (PKCE) security checks. This flaw allows an attacker who intercepts a login code to gain unauthorized access to the user's account without the required security verifier. Exploitation requires the victim to follow a specific sequence of pages and the attacker to intercept the authorization code. Red Hat rates this vulnerability as moderate severity with a CVSS score of 6.8. No patch or mitigation currently meets Red Hat's criteria for deployment and ease of use.

Impact

An attacker who intercepts a login authorization code after a user visits the password reset page can bypass PKCE security checks and gain unauthorized access to the user's account. This leads to confidentiality and integrity impacts, allowing the attacker to read and modify sensitive data and impersonate the user. The vulnerability does not affect availability. Exploitation requires the attacker to intercept the authorization code and the victim to navigate a specific sequence of pages.

Summary

The vulnerability in Red Hat Build of Keycloak's keycloak-services component involves missing authorization checks for PKCE during login initiated after password reset. This bypass allows an attacker who intercepts the authorization code to exchange it for tokens and impersonate the user. The root cause is the failure to enforce client-level mandatory PKCE requirements when creating authorization sessions via the login-actions entry point. Red Hat has assessed the severity as moderate due to the required user interaction and attack complexity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 07:50 UTC

Technical details

References

Community reviews

Related threats