Keycloak DCR Claim Name Restriction Bypass (Privilege Escalation)
CVE-2026-96547 Published on November 6, 2026

Keycloak-services: keycloak-services: dcr registration-time claim-path gap allows forging realm_access.roles
A flaw was found in the Dynamic Client Registration component of Keycloak, an open-source identity and access management solution. The issue occurs because the system does not properly restrict which claim names can be used when setting up new clients. An attacker with valid registration credentials could create a client that incorrectly maps standard user profile information to sensitive security roles, potentially allowing them to gain unauthorized privileges on external applications that trust Keycloak tokens.

NVD

Vulnerability Analysis

CVE-2026-96547 can be exploited with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, a high impact on integrity, and no impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
LOW
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
NONE
Integrity Impact:
HIGH
Availability Impact:
NONE

Timeline

Reported to Red Hat.

Made public. 43 days later.

Weakness Type

What is an AuthZ Vulnerability?

The software does not perform an authorization check when an actor attempts to access a resource or perform an action.

CVE-2026-96547 has been classified to as an AuthZ vulnerability or weakness.


Products Associated with CVE-2026-96547

stack.watch emails you whenever new vulnerabilities are published in Red Hat Build Keycloak or Red Hat Single Sign On. Just hit a watch button to start following.

Affected Versions

Red Hat Build of Keycloak: Red Hat Build of Keycloak: Red Hat Single Sign-On 7: