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

Severity: medium · CVSS 6.5 · Published 2026-06-25

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

Technologies: org.keycloak:keycloak-services (Maven). Vendors: Maven.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Medium severity, with a CVSS score of 6.5, published 25 June 2026.
Which products and versions are affected?
org.keycloak:keycloak-services (Maven) < 26.6.4, ECOSYSTEM:introduced=0.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected?
Check whether you run org.keycloak:keycloak-services (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • org.keycloak:keycloak-services (Maven) < 26.6.4, ECOSYSTEM:introduced=0

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.