---
id: "GHSA-q929-g23j-2rc7"
kind: "vulnerability"
aliases: ["GHSA-q929-g23j-2rc7"]
title: "Duplicate Advisory: Keycloak: Attacker can re-enable and take over disabled clients via registration access token"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "withdrawn"
category: "package"
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"]
published_at: "2026-06-25T18:30:41+00:00"
first_seen_at: "2026-10-29T16:39:02+00:00"
updated_at: "2026-10-29T16:39:57+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-q929-g23j-2rc7", "first_seen_at": "2026-10-29T16:39:02+00:00"}]
---

# Duplicate Advisory: Keycloak: Attacker can re-enable and take over disabled clients via registration access token

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, check and fix written by a model from the sources; labelled as such._

## Affected

- maven:org.keycloak:keycloak-services affected < 26.6.4 fixed ?

## How to check

- Check the Keycloak version with `kc.sh --version` or the server's admin console and compare it with the fixed range.
- 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.

## Timeline

- 2026-10-29T16:39:02+00:00 ghsa https://github.com/advisories/GHSA-q929-g23j-2rc7

## From the sources

### Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-r7rc-c989-86g6. This link is maintained to preserve external references.

### Original 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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_