CVE-2026-17526: Keycloak-services: keycloak-services: privilege escalation via impersonation role allows takeover of realm administrator accounts

Published Jul 27, 2026
·
Updated

A flaw was found in Keycloak. A user holding only the impersonation realm-management client role can impersonate any enabled, non-service-account user in the realm, including full realm administrators. The impersonation endpoint restricts service accounts as targets but performs no privilege-level check on the target user. After impersonating an administrator, the attacker obtains a valid SSO session and can exchange it for a fully signed access token via a standard OIDC authorization-code flow, gaining complete administrative control over the realm (read/write all users, clients, roles, password resets). The impersonation role is designed as a lesser delegation for support staff, and this flaw defeats that separation.

Other sources

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.

— MITRE

Affected Software

1 affected component
Keycloak Keycloak

Event History

Jul 27, 2026
Data Sourced
via Red Hat·08:40 AM
DescriptionSeverityAffected Software
Sep 16, 2026
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which accounts are at risk of being taken over?

Any enabled, non-service-account user in the affected realm can be impersonated, including users with full realm-administrator privileges. Service accounts are restricted as impersonation targets.

2

What access does an attacker need before exploitation?

The attacker must already hold the impersonation realm-management client role. No interaction from the target user is required.

3

How does impersonation become full administrative access?

After impersonating an administrator, the attacker receives a valid SSO session and can use a standard OIDC authorization-code flow to obtain a signed access token. That token provides complete administrative control over the realm, including management of users, clients, roles, and password resets.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203