CVE-2026-9795: Keycloak: keycloak: privilege escalation via improper scope mapping enforcement
A flaw was found in Keycloak's Fine-Grained Admin Permissions (FGAPv2) feature. An administrator with limited client management permissions can exploit this vulnerability to assign any realm role, including highly privileged roles, to a client's scope mapping. This bypasses intended security controls, allowing the injected role to be projected into a user's authentication token when they access the modified client. This could lead to unauthorized privilege escalation within the Keycloak realm.
Security readout for executives and security teams
Plain-English summary
A limited Keycloak administrator could overstep intended permissions and add powerful realm roles to a client. Those roles may then appear in user tokens for that client, creating a path to unauthorized access inside the realm. The issue is serious but requires an already privileged administrator and user interaction.
Executive priority
Treat this as a high-priority identity-platform fix where Keycloak delegates client administration. It can turn a constrained admin role into broader realm influence, affecting access decisions across applications that trust Keycloak tokens.
Technical view
The flaw affects Keycloak FGAPv2 scope mapping enforcement. A high-privilege but constrained admin can assign arbitrary realm roles, including privileged roles, to client scope mappings. When users access the altered client, the injected roles can be projected into authentication tokens. CVSS is 7.3 with high privileges, high complexity, and changed scope.
Likely exposure
Exposure is most likely in Red Hat build of Keycloak 26.4 and 26.6 deployments using FGAPv2 with delegated client administration. The bundle lists specific affected package builds and unaffected 26.4.13 or 26.6.4 product lines, but exact fixed package mapping should be confirmed against Red Hat errata.
Exploitation context
The source bundle does not indicate CISA KEV listing or active exploitation. Abuse requires an administrator with limited client management permissions, network access, and user interaction. The main risk is privilege escalation through manipulated client scope mappings and resulting tokens.
Researcher notes
Evidence is vendor-sourced. The affected condition centers on FGAPv2 authorization checks for client scope mapping changes. Do not assume unauthenticated exploitation. Focus validation on package version, FGAPv2 use, delegated admin roles, and whether privileged realm roles were added to client mappings.
Mitigation direction
Review Red Hat advisories RHSA-2026:30049, 30050, 30083, and 30084.
Update affected Red Hat build of Keycloak packages per Red Hat guidance.
Restrict delegated client administration until fixed builds are deployed.
Audit client scope mappings for unexpected privileged realm roles.
Review token role claims for sensitive clients after remediation.
Validation and detection
Inventory Red Hat build of Keycloak 26.4 and 26.6 deployments.
Identify whether FGAPv2 and delegated client management are enabled.
Compare installed package builds against Red Hat CVE and CSAF VEX data.
Check clients for unauthorized realm role scope mappings.
Confirm updated builds are no longer listed as affected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-266 · source CWE mapping
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.