Privilege escalation via incorrect realm authorization check
Published Mar 26, 2026 · Updated Mar 26, 2026
Privilege escalation in Red Hat build of Keycloak allows remote authenticated users with manage-clients permission to gain realm-wide control. RealmPermissionsV2 treats the admin-permissions resource server like an ordinary client instead of requiring manage-realm authorization. Exploitation requires realm-level admin permissions to be enabled and an account holding manage-clients, after which roles, users, and other realm functions become controllable.
Summary
What happened
Privilege escalation in Red Hat build of Keycloak allows remote authenticated users with manage-clients permission to gain realm-wide control. RealmPermissionsV2 treats the admin-permissions resource server like an ordinary client instead of requiring manage-realm authorization. Exploitation requires realm-level admin permissions to be enabled and an account holding manage-clients, after which roles, users, and other realm functions become controllable.
The record
- CVE
- CVE-2026-3121
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat JBoss Enterprise Application Platform Expansion Pack
- Classifications
- CWE-266, T1068
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo