Skip to main content
Mallory
HighVulnerability

CVE-2026-9795: Keycloak FGAPv2 Scope-Mapping Privilege Escalation

Published May 28, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.3High · v3.1
EPSS0.35%30th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Red Hat
IdentifiersCVE-2026-9795CWE-266 · Incorrect Privilege Assignment

CVE-2026-9795 is an improper privilege-assignment vulnerability in Keycloak Fine-Grained Admin Permissions v2 (FGAPv2). Missing per-role authorization enforcement in client scope-mapping administration permits a delegated administrator with limited management rights for a client to add arbitrary realm roles, including highly privileged roles, to that client’s scope mapping. The injected roles can subsequently be included in authentication tokens issued to users accessing the modified client, bypassing intended separation between client-level delegated administration and realm-level role assignment.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can poison a client’s scope mapping with privileged realm roles. Authentication tokens subsequently issued through that client can project those unintended roles to downstream users, resulting in unauthorized privilege escalation within the Keycloak realm. The attacker does not directly receive the privileged role; instead, the flaw affects tokens issued to users authenticating through the modified client.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable FGAPv2 where operationally feasible, since deployments without FGAPv2 enabled are not affected. Restrict or review delegated administrative permissions on clients, especially fine-grained client management rights that permit scope-mapping changes. Audit client scope mappings for unauthorized realm-role assignments, review whether full scope is allowed on sensitive clients, and monitor for anomalous changes to client configuration and role mappings until patched releases are deployed.

Remediation

Patch, then assume compromise.

Upgrade org.keycloak:keycloak-services to version 26.6.4 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Red HatBuild Of Keycloakapplication
FAQ

Frequently asked questions

Is CVE-2026-9795 exploited in the wild?
As of Sep 28, 2026, Mallory has no reports of CVE-2026-9795 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-9795?
As of Sep 28, 2026, Mallory has found no public exploit for CVE-2026-9795.
Is there a patch for CVE-2026-9795?
Upgrade org.keycloak:keycloak-services to version 26.6.4 or later.
What products are affected by CVE-2026-9795?
Red Hat Build Of Keycloak.
How severe is CVE-2026-9795?
CVE-2026-9795 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 0.35% (30th percentile) as of Sep 28, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.