No advisories yet.
Solution
No solution given by the vendor.
Workaround
To mitigate this issue, restrict network access to the Keycloak Dynamic Client Registration endpoint. Configure network firewalls to allow connections only from trusted hosts or networks that legitimately require access to this functionality. This limits the exposure of the vulnerable endpoint to unauthorized access attempts.
Thu, 25 Jun 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Keycloak's client registration service. A remote attacker, possessing a previously issued Registration Access Token (RAT), could exploit this vulnerability to re-enable a client that an administrator had explicitly disabled. This bypasses security controls, allowing the attacker to reset the client's secret and potentially regain privileged API access. The primary impact includes unauthorized information disclosure and potential integrity compromise. | |
| Title | Keycloak: keycloak: attacker can re-enable and take over disabled clients via registration access token | |
| First Time appeared |
Redhat
Redhat build Keycloak |
|
| Weaknesses | CWE-613 | |
| CPEs | cpe:/a:redhat:build_keycloak: | |
| Vendors & Products |
Redhat
Redhat build Keycloak |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-06-25T16:17:46.330Z
Reserved: 2026-05-27T12:48:48.084Z
Link: CVE-2026-9705
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-25T18:45:03Z