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
- Updated
- Reserved
- Assigned by
- redhat
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVDNVD · Awaiting Analysis | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.36% · top 70% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Weakness
Affected products
Red Hat · Red Hat build of Keycloak 26.4
- unaffected 26.4.17-2 – < *
Red Hat · Red Hat build of Keycloak 26.4
- unaffected 26.4-29 – < *
Red Hat · Red Hat build of Keycloak 26.4
- unaffected 26.4-30 – < *
Red Hat · Red Hat build of Keycloak 26.4.17
All versions: unaffected
Red Hat · Red Hat build of Keycloak 26.4.17
All versions: unaffected
Red Hat · Red Hat build of Keycloak 26.4.17
All versions: unaffected
Red Hat · Red Hat build of Keycloak 26.6
- unaffected 26.6.8-2 – < *
Red Hat · Red Hat build of Keycloak 26.6
- unaffected 26.6-24 – < *
Red Hat · Red Hat build of Keycloak 26.6
- unaffected 26.6-24 – < *
Red Hat · Red Hat build of Keycloak 26.6.8
All versions: unaffected
Red Hat · Red Hat build of Keycloak 26.6.8
All versions: unaffected
Red Hat · Red Hat build of Keycloak 26.6.8
All versions: unaffected
Red Hat · Red Hat Single Sign-On 7
All versions: unaffected
What to do
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)
References (6)
- RHSA-2026:95759 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:95760 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:95761 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:95762 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-92857 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2535817 (opens in a new tab)issue-trackingx_refsource_REDHAT
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-92857)Record last updated .