CVE-2026-92857
Awaiting Analysis Awaiting Analysis - Queue

Keycloak Identity Forgery via Dynamic Client Registration

Vulnerability report for CVE-2026-92857, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-05

Last updated on: 2026-11-06

Assigner: redhat-SADP

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-05
Last Modified
2026-11-06
Generated
2026-11-08
AI Q&A
2026-11-05
EPSS Evaluated
2026-11-06
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Red Hat Red Hat Build of Keycloak *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Keycloak's Dynamic Client Registration (DCR) allows attackers with a valid Initial Access Token and a realm account to forge identity information in signed security tokens. The flaw occurs because Keycloak does not properly validate the claim.name field in protocol mappers, enabling attackers to overwrite protected fields like user ID (sub) or intended audience (aud). This lets them create tokens that impersonate other users or gain unauthorized access to services relying on these tokens.

Detection Guidance

Monitor Keycloak logs for suspicious Dynamic Client Registration (DCR) activities, such as unauthorized client registrations or modifications to protocol mappers. Check for tokens with unexpected 'sub' or 'aud' claims. Use Keycloak admin console to review recently registered clients and their mapper configurations for anomalies.

Impact Analysis

An attacker could impersonate other users, gaining unauthorized access to their accounts and sensitive data. They might also bypass authentication to access protected resources or perform actions on behalf of other users. This could lead to data breaches, privilege escalation, or unauthorized transactions depending on the services using Keycloak for identity verification.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR's data protection principles or HIPAA's security requirements. It may result in data breaches, unauthorized disclosures, or lack of auditability, potentially leading to regulatory fines, legal liabilities, and reputational damage for organizations handling sensitive data.

Mitigation Strategies

Disable Dynamic Client Registration (DCR) if not required. Restrict Initial Access Token (IAT) usage to trusted entities only. Review and remove any unnecessary protocol mappers that modify reserved claims like 'sub' or 'aud'. Monitor for unauthorized token issuance and client registrations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-92857. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...