Red Hat build of Keycloak 26.4
Keycloak-services: keycloak-services: client manager can substitute sessionless token principal via hardcoded-claim mappers to obtain realm administrator authority
A flaw was found in the protocol mapper and identity resolution components of Keycloak. The issue occurs when a client manager uses hardcoded-claim mappers to override identity claims in sessionless service-account tokens. Because these tokens lack a session ID, Keycloak may incorrectly resolve the token bearer as a different, highly privileged user based on the manipulated claims. This can allow an attacker with limited client management permissions to impersonate a realm administrator and gain full control over the realm.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Fixed in 26.4.17-2
Fixed in 26.4-29
Fixed in 26.4-30
Fixed in 26.6.8-2
Fixed in 26.6-24
Fixed in 26.6-24
Mitigation
Upgrade Red Hat build of Keycloak 26.4 to 26.4.17-2 or later.
Upgrade Red Hat build of Keycloak 26.4 to 26.4-29 or later.
Upgrade Red Hat build of Keycloak 26.4 to 26.4-30 or later.
Upgrade Red Hat build of Keycloak 26.6 to 26.6.8-2 or later.
Upgrade Red Hat build of Keycloak 26.6 to 26.6-24 or later.
Upgrade Red Hat build of Keycloak 26.6 to 26.6-24 or later.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to prevent identity resolution in Keycloak from reconstructing authenticated UserModel principals from post-mapper claims in sessionless service-account tokens: upgrade to Keycloak 26.4.17, 26.6.8 (or the fixed Rhbk/Keycloak Rhel/Keycloak Services builds), which validates the integrity of identity claims in sessionless service-account tokens and prevents resolving authenticated identities from manipulated post-mapper claims, closing all 2 injection vectors (hardcoded-claim protocol mapper manipulation, sessionless token principal substitution). Until patched, this is a concern on Keycloak deployments with OIDC clients configured for sessionless service-account tokens where delegated users hold manage-clients permissions, so Audit and restrict manage-clients permissions on OIDC clients, avoid using sessionless service-account tokens, and monitor client protocol mappers for unauthorized sub or preferred_username overrides. As a compensating measure, Detect unauthorized addition of hardcoded-claim protocol mappers to Keycloak OIDC client configurations by monitoring application configurations against a declared baseline via drift detection. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper identity resolution defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1007 Application Configuration Drift Detection (IaC Enforcement) (medium)
References
- Vendor advisory access.redhat.com/errata/RHSA-2026:95759
- Vendor advisory access.redhat.com/errata/RHSA-2026:95760
- Vendor advisory access.redhat.com/errata/RHSA-2026:95761
1 more
- Vendor advisory access.redhat.com/errata/RHSA-2026:95762
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.