CVE-2026-9705 | Keycloak: keycloak: attacker can re-enable and take over disabled clients via registration access token

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.

Published: 2026-06-25 Last update: 2026-07-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-9705 is rated Low Risk (33/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.28%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-9705

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-26 — 0.28% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-9705

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2026-9705

GitHub Security Advisory for CVE-2026-9705

GHSA-q929-g23j-2rc7 · Severity: medium — A flaw was found in Keycloak's client registration service. A remote attacker, possessing a...

OS Trackers for CVE-2026-9705

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2026-9705

Affected software / configurations for CVE-2026-9705

Vendor Product Version Raw CPE
redhat build_of_keycloak >= 26.4, < 26.4.13 cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:*
redhat build_of_keycloak >= 26.6, < 26.6.4 cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:*

References for CVE-2026-9705

cvelogic Threat Intelligence