Red Hat · Keycloak · published 2026-08-05
CVE-2026-15572Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation
Routine No exploitation evidence; EPSS 0.7%.
CVE-2026-15572 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 52% of all CVEs. This Keycloak vulnerability: CVSS 8.8 (v3.1), a successful attack gives total control of the component. Fixed upstream in Keycloak 26.7.1, 26.6.5, 26.4.14. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Keycloak 26.7.1, 26.6.5, 26.4.14.
Patch events
Identity & secretsKeycloak
Keycloak security releases: 26.7.1, 26.6.5, 26.4.14
Upgrade to
26.7.126.6.526.4.14Why: Vendor security release for server software (most severe: CVE-2026-15572).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (52th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Red Hat Red Hat build of Keycloak 26.4
26.4.14-1to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.4
26.4-22to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.4
26.4-22to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.4.14
- Red Hat Red Hat build of Keycloak 26.6
26.6.5-1to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.6
26.6-11to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.6
26.6-11to before*(unaffected)
- Red Hat Red Hat build of Keycloak 26.6.5
Description (from the CVE record)#
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.
Quoted from the CVE Program record.