# CVE-2026-15572: Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation

> An attacker with client registration privileges can bypass protocol mapper restrictions to gain full administrative access to the Keycloak realm.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BIT-keycloak-2026-15572, GHSA-cj2r-7gqh-wx4f

## What is CVE-2026-15572?

CVE-2026-15572 is a high-severity vulnerability in Redhat Build of Keycloak, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-15572?

1 open source package ship an affected version, including keycloak. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keycloak` | Bitnami | From 26.4.0 | 26.4.14, 26.6.5 |

Products: Redhat Build of Keycloak.

## How do I fix CVE-2026-15572?

Upgrade keycloak to a fixed version for your release line: 26.4.14 or 26.6.5.

## Is CVE-2026-15572 being exploited?

There is no known exploitation of CVE-2026-15572 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)
- [CVE-2026-11800](https://insights.sbomify.com/CVE-2026-11800/): Org.keycloak:keycloak-services: keycloak: authentication bypass via jwt algorithm confusion (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15572 and fix it if it is affected.

What it is: CVE-2026-15572 is a high-severity vulnerability in Redhat Build of Keycloak, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15572 in the wild and no public exploit code.

Affected packages and fixed versions:
- keycloak (Bitnami): affected from 26.4.0; fixed in 26.4.14, 26.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15572/ (Markdown: https://insights.sbomify.com/CVE-2026-15572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15572
- OSV: https://osv.dev/vulnerability/CVE-2026-15572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15572/
Summaries are generated and may contain mistakes; the official description above is the record.