CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NHigh (8.1) in red hat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExplain CVE-2026-92857 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92857?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92857?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92857 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat build of Keycloak 26.4 | 26.4.17-2 |
| Red Hat build of Keycloak 26.4 | 26.4-29 |
| Red Hat build of Keycloak 26.4 | 26.4-30 |
| Red Hat build of Keycloak 26.6 | 26.6.8-2 |
| Red Hat build of Keycloak 26.6 | 26.6-24 |
Red Hat rates this Important.
The Red Hat Product Security team has assessed the severity of this vulnerability as Important, given that exploitation requires the attacker to possess a valid Initial Access Token and a realm account. Successful exploitation allows an attacker to forge identity claims in signed tokens, leading to user impersonation across access tokens, ID tokens, and UserInfo responses. The vulnerability's root cause is a lack of validation for the claim.name field in protocol mapper configurations during Dynamic Client Registration.
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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-operator-bundle:26.4.17-2 | Fixed 2026-11-06 | RHSA-2026:95760 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9:26.4-29 | Fixed 2026-11-06 | RHSA-2026:95760 |
| Red Hat build of Keycloak 26.4 | rhbk/keycloak-rhel9-operator:26.4-30 | Fixed 2026-11-06 | RHSA-2026:95760 |
| Red Hat build of Keycloak 26.4.17 | keycloak/rhbk-openshift-rhel9 | Fixed 2026-11-06 | RHSA-2026:95759 |
| Red Hat build of Keycloak 26.4.17 | keycloak-services | Fixed 2026-11-06 | RHSA-2026:95759 |
| Red Hat build of Keycloak 26.4.17 | rhbk/keycloak-rhel9 | Fixed 2026-11-06 | RHSA-2026:95759 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-operator-bundle:26.6.8-2 | Fixed 2026-11-06 | RHSA-2026:95762 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-rhel9:26.6-24 | Fixed 2026-11-06 | RHSA-2026:95762 |
| Red Hat build of Keycloak 26.6 | rhbk/keycloak-rhel9-operator:26.6-24 | Fixed 2026-11-06 | RHSA-2026:95762 |
| Red Hat build of Keycloak 26.6.8 | keycloak/rhbk-openshift-rhel9 | Fixed 2026-11-06 | RHSA-2026:95761 |
| Red Hat build of Keycloak 26.6.8 | keycloak-services | Fixed 2026-11-06 | RHSA-2026:95761 |
| Red Hat build of Keycloak 26.6.8 | rhbk/keycloak-rhel9 | Fixed 2026-11-06 | RHSA-2026:95761 |
| Red Hat Single Sign-On 7 | keycloak-services | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92857.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).