CVE-2026-9795: Keycloak privilege escalation in Fine-Grained Admin Permissions

CVE-2026-9795 · Severity: high · CVSS 7.3 · Published 2026-05-28

Keycloak, an open-source identity and access management solution, contains a vulnerability in its fine-grained administrative permissions. An administrator with restricted permissions can bypass security controls to assign highly privileged roles to themselves or others. This could lead to a full takeover of the Keycloak realm and unauthorized access to sensitive corporate data and applications.

Technologies: Keycloak, org.keycloak:keycloak-services (Maven), Red Hat build of Keycloak. Vendors: Keycloak, Maven, Red Hat.

Quick answers

Is CVE-2026-9795 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-9795 being exploited in the wild.
How severe is CVE-2026-9795?
High severity, with a CVSS score of 7.3, published 28 May 2026.
Which products and versions are affected?
Keycloak < 26.6.4; org.keycloak:keycloak-services (Maven) < 26.6.4, ECOSYSTEM:introduced=0,fixed=26.6.4; Red Hat build of Keycloak 26.4, 26.6.
Is there a fix for CVE-2026-9795?
Yes. org.keycloak:keycloak-services (Maven): upgrade to 26.6.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-9795 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-9795?
Check whether you run Keycloak, org.keycloak:keycloak-services (Maven) or Red Hat build of Keycloak at an affected version. 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.

How to fix

  • org.keycloak:keycloak-services (Maven): upgrade to 26.6.4 or later
    # set org.keycloak:keycloak-services to 26.6.4 in your pom.xml or build.gradle

Technical details

A privilege escalation vulnerability exists in Keycloak's Fine-Grained Admin Permissions (FGAPv2) feature due to improper scope mapping enforcement. Specifically, the ScopeMappedResource and ScopeMappedClientResource components failed to properly validate 'requireMapClientScope' permissions. An attacker with limited client management administrative privileges can exploit this to assign any realm role, including high-privilege roles, to a client's scope mapping. When a user subsequently authenticates via that modified client, the unauthorized roles are injected into their authentication token. This allows the attacker to escalate their privileges within the Keycloak realm. The issue is fixed in version 26.6.4.

Affected products

  • Keycloak Keycloak < 26.6.4
  • Red Hat Red Hat build of Keycloak 26.4, 26.6

Identifiers

  • CVE-2026-9795
  • GHSA-32h4-44jj-c5vx

Timeline

  • 2026-06-25: disclosed: Issue opened in Keycloak repository
  • 2026-06-26: advisory: Initial advisory published by Red Hat and Keycloak
  • 2026-07-01: patched: Fix merged and version 26.6.4 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.