CVE-2026-92857

Keycloak-services: keycloak-services: dcr protocol mapper config not validated, allowing iat holders to forge sub and aud claims in signed tokens

Published Nov 5, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.

Remediation

Vendor Workaround

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to validate protocol mapper claim.name configurations during Dynamic Client Registration to deny mapping to reserved identity claims: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the corresponding fixed Red Hat builds), which validate and reject protocol mapper configurations in Dynamic Client Registration that assign reserved claims to claim.name, closing all 2 injection vectors (Dynamic Client Registration protocol mapper configuration mapping user profile attributes to the sub claim, Dynamic Client Registration protocol mapper configuration mapping user profile attributes to the aud claim). Until patched, this is a concern on Keycloak deployments enabling Dynamic Client Registration where users possess an Initial Access Token and editable realm profile attributes, so restrict issuance of Initial Access Tokens, monitor new client registrations, and restrict user capabilities to edit profile attributes. As a compensating measure, detect unauthorized Dynamic Client Registration creations and protocol mapper changes by alerting on configuration drift against declared realm baselines and log Dynamic Client Registration events and mapper configurations to a SIEM to identify unauthorized clients mapping reserved token claims. These controls limit blast radius and contain exploitation, but they do not fix the underlying unvalidated protocol mapper claim.name defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:/a:redhat:build_keycloak: cpe:/a:redhat:build_keycloak:26.4::el9
cpe:/a:redhat:build_keycloak:26.6::el9
References
Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Build Of Keycloak 26.4
Redhat build Of Keycloak
Redhat single Sign-on
Vendors & Products Red Hat
Red Hat red Hat Build Of Keycloak 26.4
Redhat build Of Keycloak
Redhat single Sign-on
Type Values Removed Values Added
Description Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.
Title Keycloak-services: keycloak-services: dcr protocol mapper config not validated, allowing iat holders to forge sub and aud claims in signed tokens
First Time appeared Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
Weaknesses CWE-20
CPEs cpe:/a:redhat:build_keycloak:
cpe:/a:redhat:red_hat_single_sign_on:7
Vendors & Products Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 9, 2026, 5:22 PM
Reserved
Sep 17, 2026, 5:11 AM
Status
Awaiting Analysis
Published
Nov 5, 2026, 6:17 PM
Modified
Nov 9, 2026, 6:17 PM
Severity
Important
Public date
Nov 5, 2026, 12:00 AM