# CVE-2026-96547: Keycloak Dynamic Client Registration privilege escalation

Source: https://junglewise.ai/threats/cve-2026-96547-a-flaw-was-found-in-the-dynamic-client-registration-component-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-96547 · Severity: medium · CVSS 6.5 · Published 2026-11-06

Keycloak is an open-source identity management system that issues security tokens used by applications to verify user identity and permissions. A flaw in its client registration component allows an authenticated attacker to manipulate security claims in tokens, potentially granting themselves unauthorized admin or other elevated roles on any application that trusts Keycloak's tokens, effectively taking over those applications.

Technologies: [Keycloak](https://junglewise.ai/threats/technologies/keycloak). Vendors: [Keycloak](https://junglewise.ai/threats/vendors/keycloak).

## Quick answers

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

**How severe is CVE-2026-96547?** Medium severity, with a CVSS score of 6.5, published 6 November 2026.

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

**Is there a fix for CVE-2026-96547?** 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-96547 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-96547?** Check whether you run 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

The Dynamic Client Registration component fails to properly restrict which claim names can be used when configuring new clients, allowing CWE-862 (missing authorization). An attacker with valid registration credentials can create a client that maps standard user attributes to sensitive security roles like realm_access.roles, enabling privilege escalation on external relying parties. The vulnerability requires initial network access with valid credentials but results in forged authorization tokens.

## Affected products

- Keycloak Keycloak

## Timeline

- 2026-11-06: 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-96547](https://access.redhat.com/security/cve/CVE-2026-96547)

## Related threats

- [Keycloak login-failure storage synchronization error in MySQL/MariaDB](https://junglewise.ai/threats/cve-2026-112201-a-flaw-was-found-in-the-login-failure-storage-component-of)
- [Keycloak PKCE bypass in login after password reset](https://junglewise.ai/threats/cve-2026-125652-a-flaw-was-found-in-the-keycloak-services-component-of-keycloak)
- [Keycloak server arbitrary code execution in client authorization](https://junglewise.ai/threats/cve-2026-120984-a-flaw-was-found-in-the-keycloak-server-s-client-management)
- [Keycloak token sanitization bypass in protocol mapper](https://junglewise.ai/threats/cve-2026-97848-a-flaw-was-found-in-the-token-sanitization-logic-of-keycloak-an)
- [Keycloak TokenManager identity rebinding in stateless token validation](https://junglewise.ai/threats/cve-2026-96447-a-flaw-was-found-in-the-tokenmanager-component-of-keycloak-an)