Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with account holding impersonation role
-
DeliveryInvoke impersonation against a realm administrator
-
ExploitMissing authorization check permits admin impersonation
-
ExecutionAssume full realm-admin session
-
ImpactManage users, clients, and roles (realm takeover)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated Keycloak account that has already been granted the realm 'impersonation' role (a delegated admin capability, hence CVSS PR:H). Given that role, the attacker impersonates a realm administrator and obtains full administrative control of the realm (users, clients, roles). Limiting factors: this is not a pre-authentication or default-config remote takeover - it depends on the attacker/insider possessing the impersonation role beforehand, so realistic risk centers on trusted sub-administrators, over-privileged support accounts, or an already-compromised delegated-admin credential. Affected: Red Hat Build of Keycloak 26.4 (before 26.4.16) and 26.6 (before 26.6.7). |
| Impact | This is a genuine but access-gated privilege-escalation issue (CWE-862, missing authorization). The Red Hat CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H = 7.2 High) is internally consistent with the description: the attacker must already hold the delegated 'impersonation' role (PR:H), so this is not a pre-auth internet-wide exploit but an escalation from an existing privileged sub-administrator to full realm administrator. There is no EPSS score, no CISA KEV listing, and no public PoC in the provided data, so exploitation status is 'no public exploit identified at time of analysis.' The signals are aligned rather than conflicting - a High CVSS driven by full C/I/A realm-admin impact, tempered by the PR:H barrier that limits the exploit population to accounts already granted impersonation rights. Real-world priority is moderate: high impact but requires a trusted-insider or already-compromised delegated-admin account. One caveat worth verifying with Red Hat: whether the required role should be scored PR:H (full delegated admin) or PR:L (a narrowly-granted impersonation permission) - that choice moves the base score and the realistic exploit population. |
| Exploit ScenarioDerived | A tenant/sub-administrator in a Keycloak realm who has been granted only the 'impersonation' role (intended to let them act as ordinary users for support) abuses the flawed authorization check to impersonate a realm administrator instead. Having assumed the admin identity, they manage users, clients, and roles across the entire realm - full administrative takeover. No public PoC is available in the provided data; exploitation requires an authenticated account that already holds the impersonation role. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Privilege escalation in Red Hat Build of Keycloak allows an account already holding the realm 'impersonation' role to impersonate a realm administrator and thereby seize full administrative control over that realm, including management of users, clients, and roles. Affected builds are 26.4 before 26.4.16 and 26.6 before 26.6.7. This is an access-gated issue rather than a pre-authentication takeover: the CVSS vector (PR:H) confirms the attacker must be an authenticated, privileged sub-administrator or holder of a compromised delegated-admin credential before exploitation is possible, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade Red Hat Build of Keycloak to 26.4.16 (for the 26.4 stream) or 26.6.7 (for the 26.6 stream) as delivered by Red Hat errata RHSA-2026:68276, RHSA-2026:68277, RHSA-2026:68278, and RHSA-2026:68280, and consult https://access.redhat.com/security/cve/CVE-2026-17526 for the authoritative affected-product matrix. Until upgrades are complete, reduce exposure by treating the realm 'impersonation' role as an administrative privilege: audit realms for composite or direct role assignments that grant impersonation to support, helpdesk, or other delegated sub-administrator accounts and remove it where the business need does not justify full-admin equivalence - the trade-off is that legitimate support impersonation workflows will stop functioning. Additionally, restrict the impersonation role to accounts whose credentials and session security match a realm administrator, enforce step-up authentication or MFA on those accounts, and monitor Keycloak admin and impersonation audit events for impersonation of realm administrators so that abuse is detected quickly, noting that these are compensating controls only and do not remove the underlying missing-authorization defect.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Keycloak is an open-source identity and access management (IAM) platform used for single sign-on, OAuth 2.0/OpenID Connect token issuance, and realm-scoped administration; Red Hat Build of Keycloak is the commercially supported distribution of the same codebase. The flaw is classified as CWE-862 (Missing Authorization): the impersonation capability is intended as a delegated support feature, but the authorization check does not adequately constrain which principal a delegated impersonator may assume, so a user who is legitimately granted the impersonation role can select a realm administrator as the impersonation target. Because the impersonation flow then issues a session/token carrying the target administrator's realm-management authorities, the delegated user acquires the full administrative surface of the realm - user administration, client registration and configuration, role and group management - rather than the narrower permissions they were originally delegated. The assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H reflects a network-reachable, low-complexity attack requiring high privileges (the pre-existing impersonation role), with high confidentiality, integrity, and availability impact confined to the single realm scope (S:U). CPE data identifies the affected packages as Red Hat Build of Keycloak 26.4 (including 26.4.16 reference points) and 26.6 (including 26.6.7 reference points), consistent with the two maintained 26.x streams being patched at those versions.
Know when Keycloak gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Attacker must already hold the privileged impersonation role (PR:H) and reaches it over the network (AV:N); successful escalation yields full realm-admin control, so C/I/A all High.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
Keycloak is an open-source identity and access management solution. A vulnerability was discovered where a user with the impersonation role can impersonate a realm administrator. This allows the attacker to gain full administrative control over the realm, including the ability to manage users, clients, and roles.
Executive ViewAI
A privilege-escalation flaw in Red Hat Build of Keycloak (26.4 before 26.4.16 and 26.6 before 26.6.7) lets a delegated sub-administrator with the realm 'impersonation' role elevate to full realm administrator, giving that person complete control over users, clients, and role assignments within the affected realm. Because Keycloak commonly serves as the identity backbone for internal and customer-facing applications, a successful escalation could allow an attacker to mint credentials, impersonate executives and service accounts, and quietly widen access across every application trusting that realm. Leadership should care because the exposure is not an external break-in but an insider or compromised-delegated-credential path to the organization's central authentication authority, and no vendor patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: revoke or tightly restrict the realm 'impersonation' role and delegated admin assignments so that no account holds both impersonation and administrative capability; enforce phishing-resistant MFA and least privilege for all privileged Keycloak accounts; limit admin console and admin REST API exposure to trusted networks or a management VPN; enable detailed admin, impersonation, and authentication event logging with alerting and forward logs to the SIEM; shorten administrative session and token lifetimes and revoke active admin sessions; and be prepared to restore realm configuration from a verified backup if unauthorized role changes or impersonation activity is detected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remot
The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote at
An unconstrained memory consumption vulnerability was discovered in Keycloak. Rated high severity (CVSS 7.7), this vulne
Due to improper authorization, Red Hat Single Sign-On is vulnerable to users performing actions that they should not be
It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly. Rated critical severit
Authentication bypass in the Apache Airflow Keycloak auth manager provider (apache-airflow-providers-keycloak below 0.10
A privilege escalation flaw was found in the token exchange feature of keycloak. Rated critical severity (CVSS 9.8), thi
A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used in
A flaw was found in keycloak in versions before 13.0.0. Rated critical severity (CVSS 9.6), this vulnerability is remote
A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to t
A flaw was found in Keycloak. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack c
A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using
EUVD-2026-80854
GHSA-j7cq-x5cp-qpcx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB