CVE-2026-96547 · Package
NO FIX YET
Keycloak's Dynamic Client Registration does not restrict which claim names a new client may use, so a client can map ordinary profile data onto security roles. An attacker holding valid registration credentials could gain privileges on external applications that trust Keycloak tokens.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-hosted Keycloak with Dynamic Client Registration enabled, where external applications trust Keycloak-issued tokens for role decisions. Deployments that do not enable dynamic registration, or that restrict registration to trusted administrators, are less exposed. The sources do not give the exact affected versions.
Not affected if dynamic-registration-disabled, managed-hosting
Who cares keycloak, oidc, self-hosted, sso
unknown for the affected range, as the sources give no product ranges.No fix yet, per the sources.
A flaw was found in the Dynamic Client Registration component of Keycloak, an open-source identity and access management solution. The issue occurs because the system does not properly restrict which claim names can be used when setting up new clients. An attacker with valid registration credentials could create a client that incorrectly maps standard user profile information to sensitive security roles, potentially allowing them to gain unauthorized privileges on external applications that trust Keycloak tokens.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
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.