A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol Mapper Types" policy, which restricts which types of data mappers a client can use, fails to re-validate the mapper type during a client update if the mapper's configuration remains unchanged. An attacker with client registration privileges can exploit this by first registering an allowed mapper type with a malicious configuration and then swapping it for a restricted, high-privilege mapper type (such as one that hardcodes administrative roles). This allows the attacker to gain full administrative access to the Keycloak realm.
References
| Link | Resource |
|---|---|
| https://access.redhat.com/errata/RHSA-2026:50846 | Vendor Advisory |
| https://access.redhat.com/errata/RHSA-2026:50847 | Vendor Advisory |
| https://access.redhat.com/errata/RHSA-2026:50848 | Vendor Advisory |
| https://access.redhat.com/errata/RHSA-2026:50849 | Vendor Advisory |
| https://access.redhat.com/security/cve/CVE-2026-15572 | Vendor Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2499592 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-08-05 16:16
Updated : 2026-08-10 19:23
NVD link : CVE-2026-15572
Mitre link : CVE-2026-15572
CVE.ORG link : CVE-2026-15572
JSON object : View
Products Affected
redhat
- build_of_keycloak
CWE
CWE-843
Access of Resource Using Incompatible Type ('Type Confusion')
