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
- High 8.1
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.
Key facts
- Published
- 5 Nov 2026
- Last changed
- 9 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.361% likely to be exploited in the next 30 days, higher than 30.378% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.1CVSS 3.1, Highfrom the CNA (redhat)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
What to do
- 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 cCNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
CNA context is abbreviated; consult the original record for the complete statements.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4 |
|
| Red Hat | Red Hat build of Keycloak 26.4.17 |
|
| Red Hat | Red Hat build of Keycloak 26.4.17 |
|
| Red Hat | Red Hat build of Keycloak 26.4.17 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6 |
|
| Red Hat | Red Hat build of Keycloak 26.6.8 |
|
| Red Hat | Red Hat build of Keycloak 26.6.8 |
|
| Red Hat | Red Hat build of Keycloak 26.6.8 |
|
| Red Hat | Red Hat Single Sign-On 7 |
|
Timeline
- 16 Sep 2026 Reported to Red Hat.
- 5 Nov 2026 Made public.
- 5 Nov 2026 Published