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: n/a
KEV: No
Impact: Identity Spoofing via forged token claims
Action: Patch Immediately
AI Analysis

Impact

The flaw in the Dynamic Client Registration flow allows the injection of user profile information into the protected fields of identity tokens, such as sub (user ID) and aud (audience). Input validation is missing, which lets an attacker holding a legitimate token with appropriate iat claims create a malicious application that issues signed security tokens containing forged subject and audience values. This enables the attacker to impersonate other users and gain unauthorized access to services that rely on these tokens for authentication, thereby breaching confidentiality and integrity.

Affected Systems

The affected products are the Red Hat Build of Keycloak and Red Hat Single Sign‑On 7. Version specifics are not supplied in the public advisory, so any deployment of these products that has not applied the vendor’s security update could be susceptible.

Risk and Exploitability

The CVSS score of 8.1 marks this flaw as high severity. No EPSS value is available, but the lack of known exploits and the requirement for a privileged token to register a client make exploitation non‑obvious. The vulnerability is not listed in the CISA KEV catalog, indicating no active exploitation campaigns are currently known, yet the high impact warrants immediate remediation. Application of the patch is the only known effective remedy; meanwhile, disabling or limiting DCR for untrusted users can reduce the attack surface.

Generated by OpenCVE AI on November 5, 2026 at 19:28 UTC.

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.


OpenCVE Recommended Actions

  • Apply the vendor’s security update for CVE-2026-92857 to the Keycloak or Single Sign‑On environment.
  • If an update cannot be applied immediately, disable or tightly restrict the Dynamic Client Registration feature for untrusted tenants and enforce least‑privilege client‑creation policies.
  • Reconfigure Keycloak protocol mappers to validate sub and aud values explicitly and reject any client‑provided mappings that override protected fields.
  • Monitor authentication and registration logs for anomalous client registrations or repeated attempts to forge identity tokens.

Generated by OpenCVE AI on November 5, 2026 at 19:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

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

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-05T17:15:24.374Z

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-05T18:17:11.013

Link: CVE-2026-92857

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-05T19:30:11Z

Weaknesses
  • CWE-20

    Improper Input Validation