# CVE-2026-92857: Keycloak Dynamic Client Registration validation bypass

Source: https://junglewise.ai/threats/cve-2026-92857-keycloak-provides-a-dynamic-client-registration-feature-that  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-05. Updated: 2026-11-05  
License: CC BY 4.0 with a link back

CVE-2026-92857 · Severity: high · CVSS 8.1 · Published 2026-11-05

Keycloak is an identity and access management system that handles user authentication and authorization for enterprise applications. A flaw in its Dynamic Client Registration feature allows attackers with valid tokens to register malicious applications and forge identity information in security tokens, potentially impersonating other users and gaining unauthorized access to dependent services.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-92857 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92857 being exploited in the wild.

**How severe is CVE-2026-92857?** High severity, with a CVSS score of 8.1, published 5 November 2026.

**Which products and versions are affected?** Red Hat Keycloak.

**Is there a fix for CVE-2026-92857?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92857 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-92857?** Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An improper input validation flaw (CWE-20) in the protocol mapper configuration during Dynamic Client Registration allows an authenticated attacker to forge identity claims in signed tokens by mapping their own profile details to protected fields (sub, aud). The vulnerability requires the attacker to possess a valid Initial Access Token and a realm account; successful exploitation results in token forgery enabling user impersonation across access tokens, ID tokens, and UserInfo responses.

## Affected products

- Red Hat Keycloak

## Timeline

- 2026-11-05: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-92857](https://access.redhat.com/security/cve/CVE-2026-92857)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak token exchange lifetime bypass in Standard Token Exchange V2](https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)