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.
Published: 2026-11-05
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

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

History

Fri, 06 Nov 2026 17:15:00 +0000

Type Values Removed Values Added
References

Fri, 06 Nov 2026 10:30:00 +0000

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

Fri, 06 Nov 2026 04:30:00 +0000

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

Fri, 06 Nov 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 threat_severity

Important

Thu, 05 Nov 2026 17:30:00 +0000

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'}

Subscriptions

Red Hat Red Hat Build Of Keycloak 26.4
Redhat Build Keycloak Build Of Keycloak Red Hat Single Sign On Single Sign-on
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-06T19:44:38.563Z

Reserved: 2026-09-17T05:11:31.222Z

Link: CVE-2026-92857

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-05T18:17:10.887

Modified: 2026-11-06T17:20:03.620

Link: CVE-2026-92857

cve-icon Redhat

Severity : Important

Publid Date: 2026-11-05T00:00:00Z

Links: CVE-2026-92857 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T04:15:11Z

Weaknesses
  • CWE-20

    Improper Input Validation