Authenticated cross-resource access via UMA permission prefix
Published Jun 25, 2026 · Updated Jun 25, 2026
Authorization bypass in Red Hat build of Keycloak allows remote authenticated users to access unauthorized typed resources. A permission request prefix reuses one valid UMA ticket so per-resource checks authorize every resource of the same type in that resource server. Exploitation requires PERMISSIVE enforcement, owner-managed access, no explicit type policy, and a granted ticket for one resource.
Summary
What happened
Authorization bypass in Red Hat build of Keycloak allows remote authenticated users to access unauthorized typed resources. A permission request prefix reuses one valid UMA ticket so per-resource checks authorize every resource of the same type in that resource server. Exploitation requires PERMISSIVE enforcement, owner-managed access, no explicit type policy, and a granted ticket for one resource.
The record
- CVE
- CVE-2026-9799
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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