VulnerabilityPublished 6 Nov 2026

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

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 provide an official fix or mitigation that meets their criteria for ease of use, deployment, and applicability. Users should monitor Red Hat's advisory for updates. Since exploitation requires valid registration credentials, controlling and monitoring client registration access is advisable as a precautionary measure.

Description

CVE-2026-96547 is a vulnerability in the Dynamic Client Registration component of Red Hat Build of Keycloak. It allows an attacker with valid registration credentials to create clients that improperly map user profile claims to sensitive security roles. This can lead to unauthorized privilege escalation on external applications that trust Keycloak tokens. The vulnerability arises from insufficient restriction on claim names during client registration. Red Hat rates this issue as moderate severity with a CVSS score of 6.5. No official patch or mitigation meeting Red Hat's criteria is currently available.

Impact

Exploitation requires an attacker to have valid initial access tokens for client registration. Successful exploitation allows forging of realm roles in tokens, potentially leading to unauthorized privilege escalation on external applications relying on Keycloak tokens for authorization. The integrity of token claims can be compromised, but confidentiality and availability impacts are not indicated. The vulnerability specifically affects external relying parties that use token claims for authorization decisions.

Summary

The vulnerability CVE-2026-96547 affects the Dynamic Client Registration feature in Red Hat Build of Keycloak. The system fails to properly restrict which claim names can be used when setting up new clients. An attacker possessing valid registration credentials can exploit this flaw to create a client that forges realm roles in tokens issued to external relying parties. This can result in privilege escalation by granting unauthorized access to sensitive roles. Red Hat's advisory confirms the root cause as a lack of claim name restriction and classifies the severity as moderate.

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