{"id":"GHSA-q929-g23j-2rc7","kind":"vulnerability","aliases":["GHSA-q929-g23j-2rc7"],"related":[],"title":"Duplicate Advisory: Keycloak: Attacker can re-enable and take over disabled clients via registration access token","description":"### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-r7rc-c989-86g6. This link is maintained to preserve external references.\n\n### Original Description\nA 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.","summary":"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.","severity":"medium","cvss":6.5,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"org.keycloak:keycloak-services","fixed":[],"affected":"< 26.6.4","ecosystem":"maven"}],"ecosystems":["maven"],"tags":["cwe-613","identity","keycloak","package","self-hosted"],"not_affected_if":["version-26.6.4-or-later"],"how_to_check":"- Check the Keycloak version with `kc.sh --version` or the server's admin console and compare it with the fixed range.\n- Look for `keycloak-services` in the Maven dependencies of any custom Keycloak extension.","fix":"- Keycloak `keycloak-services` `26.6.4` or later, per the affected range in the source.","status":"withdrawn","published_at":"2026-06-25T18:30:41+00:00","first_seen_at":"2026-10-29T16:39:02+00:00","triaged_at":"2026-10-29T16:39:57+00:00","updated_at":"2026-10-29T16:39:57+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-10-29T16:39:57Z","model":"claude-haiku-5-5","output":{"fix":"- Keycloak `keycloak-services` `26.6.4` or later, per the affected range in the source.","reach":"network","title":"Keycloak: disabled clients can be re-enabled with an old registration token","impact":"medium","summary":"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.","audience":"businesses","category":"package","nicknames":[],"who_cares":["keycloak","self-hosted","identity"],"confidence":0.6,"fix_status":"available","needs_auth":"yes","worst_case":"attacker re-enables disabled client and resets its secret","analyst_note":"","how_to_check":"- Check the Keycloak version with `kc.sh --version` or the server's admin console and compare it with the fixed range.\n- Look for `keycloak-services` in the Maven dependencies of any custom Keycloak extension.","plain_action":"","needs_analyst":false,"not_affected_if":["version-26.6.4-or-later"],"who_is_affected":"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.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"unknown"},"cost_usd":0.000687,"input_tokens":4284,"output_tokens":518,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-613':33B '2rc7':22A,27A '86g6':52B,97C 'access':16A,64B,126C,163C 'administr':73B,141C 'advisori':2A,41B,81C,83C 'allow':149C 'api':162C 'attack':4A,58B,120C,151C 'bypass':146C 'c989':51B,96C 'client':13A,71B,115C,138C,155C 'compromis':174C 'control':148C 'could':66B,129C 'cwe':32B 'descript':107C 'disabl':12A,75B,144C 'disclosur':170C 'duplic':1A,46B,80C,91C 'enabl':8A,69B,136C 'explicit':143C 'exploit':130C 'extern':104C 'flaw':109C 'found':111C 'g23j':21A,26A 'ghsa':19A,24A,49B,94C 'ghsa-q929-g23j-2rc7':18A,23A 'ghsa-r7rc-c989-86g6':48B,93C 'hold':59B 'host':39B 'ident':34B 'impact':166C 'includ':167C 'inform':169C 'integr':173C 'issu':62B,124C 'keycloak':3A,30A,35B,113C 'keycloak-services':29A 'link':99C 'maintain':101C 'org.keycloak':28A 'origin':54B,106C 'packag':36B 'possess':121C 'potenti':159C,172C 'preserv':103C 'previous':61B,123C 'primari':165C 'privileg':161C 'q929':20A,25A 'r7rc':50B,95C 'rat':128C 're':7A,68B,135C 're-en':6A,67B,134C 'refer':105C 'regain':160C 'registr':15A,63B,116C,125C 'remot':119C 'reset':77B,153C 'say':56B 'secret':79B,157C 'secur':147C 'self':38B 'self-host':37B 'servic':117C 'services':31A 'take':10A 'text':55B 'token':17A,65B,127C 'unauthor':168C 'via':14A 'vulner':132C 'withdrawn':43B,86C","nicknames":[],"mitigations":[],"who_affected":"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.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"businesses","plain_action":null,"first_public_at":"2026-06-25T18:30:41+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","cvss_by":"GitHub","poc_count":0,"sources":[{"source":"ghsa","external_id":"GHSA-q929-g23j-2rc7","url":"https://github.com/advisories/GHSA-q929-g23j-2rc7","severity":"medium","published_at":"2026-06-25T18:30:41+00:00","modified_at":"2026-10-29T16:36:18+00:00","first_seen_at":"2026-10-29T16:39:02+00:00","fetched_at":"2026-10-29T16:39:02+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}