cve.bz

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

8.1 highEPSS 0.4%Fix available

High (8.1) in red hat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat build of Keycloak 26.4: fixed in 26.4.17-2
  • Red Hat Red Hat build of Keycloak 26.4: fixed in 26.4-29
  • Red Hat Red Hat build of Keycloak 26.4: fixed in 26.4-30
  • Red Hat Red Hat build of Keycloak 26.6: fixed in 26.6.8-2
  • Red Hat Red Hat build of Keycloak 26.6: fixed in 26.6-24

Ask an AI about this CVE

Show the promptExplain 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.

Affected

  • 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.6
  • red hat:red hat build of keycloak 26.6.8
  • red hat:red hat single sign-on 7

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.426.4.17-2
Red Hat build of Keycloak 26.426.4-29
Red Hat build of Keycloak 26.426.4-30
Red Hat build of Keycloak 26.626.6.8-2
Red Hat build of Keycloak 26.626.6-24

Red Hat

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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)

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.17-2Fixed 2026-11-06RHSA-2026:95760
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9:26.4-29Fixed 2026-11-06RHSA-2026:95760
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator:26.4-30Fixed 2026-11-06RHSA-2026:95760
Red Hat build of Keycloak 26.4.17keycloak/rhbk-openshift-rhel9Fixed 2026-11-06RHSA-2026:95759
Red Hat build of Keycloak 26.4.17keycloak-servicesFixed 2026-11-06RHSA-2026:95759
Red Hat build of Keycloak 26.4.17rhbk/keycloak-rhel9Fixed 2026-11-06RHSA-2026:95759
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.8-2Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6.8keycloak/rhbk-openshift-rhel9Fixed 2026-11-06RHSA-2026:95761
Red Hat build of Keycloak 26.6.8keycloak-servicesFixed 2026-11-06RHSA-2026:95761
Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9Fixed 2026-11-06RHSA-2026:95761
Red Hat Single Sign-On 7keycloak-servicesNot 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.

Attack patterns (CAPEC)

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).

References

Check your stackJSON