VulnerabilityPublished 6 Nov 2026

CVE-2026-97848: Red Hat Build of Keycloak · Improper Input Validation

Affects Red Hat Build of KeycloakSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 6 Nov 2026, 06:20 UTC

CVSS 3.1 base score

6.5Medium

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within the impacted component.
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

Red Hat currently does not offer a mitigation or patch that meets their criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for future updates or fixes. Since exploitation requires specific privileges, restricting client registration and initial access token issuance to trusted parties can reduce risk.

Description

CVE-2026-97848 is a vulnerability in Red Hat Build of Keycloak involving improper input validation in token sanitization. When a protocol mapper is configured to emit structured claims as JSON, the security check fails to recognize Jackson JSON objects, allowing attackers with client registration privileges or a valid Initial Access Token to inject forged client roles into tokens. This could lead to unauthorized access to protected resources. Red Hat rates this vulnerability as Moderate severity with a CVSS score of 6.5. Currently, no effective mitigation or patch meeting Red Hat's criteria is available.

Impact

Exploitation requires the attacker to have existing client registration privileges or a valid Initial Access Token. Successful exploitation allows forging of client-role mappings in signed tokens, potentially granting unauthorized access to protected resources. The vulnerability impacts integrity by enabling unauthorized role injection but does not affect confidentiality or availability. There are no known exploits in the wild at this time.

Summary

This vulnerability arises from incomplete type checking in Keycloak's token sanitization logic when using protocol mappers configured with jsonType=JSON. The security mechanism only inspects standard Java maps and does not detect Jackson ObjectNode instances, enabling attackers with existing client registration privileges or valid Initial Access Tokens to inject forged client-role mappings into signed tokens. This flaw can result in unauthorized access to resource servers by manipulating security tokens. Red Hat has assessed the issue as Moderate severity (CVSS 6.5) and currently does not provide a mitigation or patch that meets their standards for ease of use, applicability, or stability.

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