Live › vulnerability › GHSA-q929-g23j-2rc7
This advisory is withdrawn as a duplicate of GHSA-r7rc-c989-86g6. The original text says an attacker holding a previously issued Registration Access Token could re-enable a client an administrator had disabled, then reset its secret.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:39 UTC. All times on this page are UTC.
The original text says the flaw is in Keycloak's client registration service, so deployments that expose client registration and have issued Registration Access Tokens are the ones to look at. Sources do not say whether default configurations are exposed. Deployments on fixed versions are not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| org.keycloak:keycloak-services | maven | < 26.6.4 | – |
kc.sh --version or the server's admin console and compare it with the fixed range.keycloak-services in the Maven dependencies of any custom Keycloak extension.keycloak-services 26.6.4 or later, per the affected range in the source.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This advisory has been withdrawn because it is a duplicate of GHSA-r7rc-c989-86g6. This link is maintained to preserve external references.
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.
This page as .md · .json · in your agent: get_signal("GHSA-q929-g23j-2rc7")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.