Unauthorized ROPC tokens via skipped client-policy conditions
Published May 28, 2026 · Updated May 28, 2026
Client-policy bypass in Red Hat build of Keycloak 26.4 and 26.6 allows remote attackers to obtain ROPC tokens despite a rejection policy. The affected providers either retrieve no client from the ROPC context or fail to trigger for that request, so reject-ropc-grant is skipped. Exposure requires a realm combining an affected condition with that executor; successful requests yield tokens and access within their scope.
Summary
What happened
Client-policy bypass in Red Hat build of Keycloak 26.4 and 26.6 allows remote attackers to obtain ROPC tokens despite a rejection policy. The affected providers either retrieve no client from the ROPC context or fail to trigger for that request, so reject-ropc-grant is skipped. Exposure requires a realm combining an affected condition with that executor; successful requests yield tokens and access within their scope.
The record
- CVE
- CVE-2026-9792
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-280, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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