Quick answers
- Is CVE-2026-97847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97847 being exploited in the wild.
- How severe is CVE-2026-97847?
- High severity, with a CVSS score of 7.1, published 5 November 2026.
- Which products and versions are affected?
- Red Hat Keycloak.
- Is there a fix for CVE-2026-97847?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-97847 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-97847?
- Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Keycloak's protocol mapper and identity resolution components when hardcoded-claim mappers are used to modify sessionless service-account tokens. Because these tokens lack a session ID, Keycloak fails to properly validate token integrity and incorrectly resolves the token bearer as a different privileged user based on manipulated claims. An attacker with client management privileges can exploit this improper authentication mechanism (CWE-287) to escalate to realm administrator authority.
Affected products
- Red Hat Keycloak
Timeline
- 2026-11-05: disclosed