Client takeover via unchecked disabled state
Published Jun 25, 2026 · Updated Jun 25, 2026
Access-control bypass in Red Hat build of Keycloak 26.4 before 26.4.13 and 26.6 before 26.6.4 allows remote attackers to take over disabled clients. ClientRegistrationAuth accepts a previously issued RAT for view and update operations without checking whether an administrator disabled the target client. Possession of that client-specific token is required; the attacker can re-enable the client, rotate its secret, and resume its authorized API access.
Summary
What happened
Access-control bypass in Red Hat build of Keycloak 26.4 before 26.4.13 and 26.6 before 26.6.4 allows remote attackers to take over disabled clients. ClientRegistrationAuth accepts a previously issued RAT for view and update operations without checking whether an administrator disabled the target client. Possession of that client-specific token is required; the attacker can re-enable the client, rotate its secret, and resume its authorized API access.
The record
- CVE
- CVE-2026-9705
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-613, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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