CVE-2026-97847

Keycloak-services: keycloak-services: client manager can substitute sessionless token principal via hardcoded-claim mappers to obtain realm administrator authority

  • High 7.1

Description

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.

Key facts

Published
5 Nov 2026
Last changed
9 Nov 2026
Assigned by
redhat
EPSS
0.315% likely to be exploited in the next 30 days, higher than 24.786% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.1CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

What to do

  • 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 mCNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4.17-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-29 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-30 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6.8-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: unaffected

Timeline

  1. 24 Sep 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References