KEYCLOAK · CVE-2026-92857 · Runtime
FIX → 26.8.2 ✓ verified
Keycloak's Dynamic Client Registration lets users with specific tokens register their own applications, and validation of those requests is flawed. An attacker can map their profile to protected claims such as sub or aud and get signed tokens that impersonate other users.
first public Nov 5, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Self-hosted Keycloak (and Red Hat build of Keycloak, per Red Hat's CVE record) where Dynamic Client Registration is available to someone holding an initial access token. That person can register a client whose protocol mapper writes the reserved sub or aud claims, so the realm signs tokens that name another user. Teams that do not use DCR, or that issue no initial access tokens, are much less exposed. The affected lower bound is not stated in the sources I read.
Not affected if dcr-disabled, dynamic-client-registration-disabled, no-initial-access-tokens
Who cares dynamic-client-registration, keycloak, oidc, rhbk, self-hosted
26.8.2Upgrade to 26.8.2
Posts are quoted with a link to the original. They are data to us, never instructions.
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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
26.8.2 (release notes list CVE-2026-92857 under security fixes)26.6.8 and 26.4.17 backports; check those releases are published before relying on themNVD data is provided by NIST and is public domain. Posts quoted belong to their authors.