CVE-2026-9705

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
18.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: redhat.
redhat

2481878 – (CVE-2026-9705) CVE-2026-9705 keycloak: Keycloak: Attacker can re-enable and take over disabled clients via Registration Access Token

https://bugzilla.redhat.com/show_bug.cgi?id=2481878
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-9705

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.6-82026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 02:29 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 22:21 UTCVendor advisory
  7. 2026-07-16 22:21 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 20:56 UTCVendor advisory
  10. 2026-07-15 20:56 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-14 19:28 UTCVendor advisory
  14. 2026-07-14 19:28 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 18:03 UTCVendor advisory
  17. 2026-07-13 18:02 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 16:37 UTCVendor advisory
  20. 2026-07-12 16:37 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 15:12 UTCVendor advisory
  23. 2026-07-11 15:12 UTCGHSA enrichment
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-10 13:48 UTCVendor advisory
Show 42 more
  1. 2026-07-10 13:48 UTCGHSA enrichment
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 12:19 UTCVendor advisory
  4. 2026-07-09 12:19 UTCGHSA enrichment
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 10:55 UTCVendor advisory
  7. 2026-07-08 10:55 UTCGHSA enrichment
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 09:31 UTCVendor advisory
  10. 2026-07-07 09:31 UTCGHSA enrichment
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 08:06 UTCVendor advisory
  13. 2026-07-06 08:06 UTCGHSA enrichment
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 06:41 UTCVendor advisory
  16. 2026-07-05 06:41 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 05:14 UTCVendor advisory
  20. 2026-07-04 05:14 UTCGHSA enrichment
  21. 2026-07-03 03:50 UTCVendor advisory
  22. 2026-07-03 03:49 UTCGHSA enrichment
  23. 2026-07-02 02:13 UTCVendor advisory
  24. 2026-07-02 02:13 UTCGHSA enrichment
  25. 2026-07-01 15:07 UTCEPSS rescore
  26. 2026-07-01 00:50 UTCVendor advisory
  27. 2026-07-01 00:50 UTCGHSA enrichment
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-29 23:26 UTCVendor advisory
  30. 2026-06-29 23:26 UTCGHSA enrichment
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-28 22:03 UTCVendor advisory
  33. 2026-06-28 22:03 UTCGHSA enrichment
  34. 2026-06-28 14:07 UTCEPSS rescore
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-27 20:39 UTCVendor advisory
  37. 2026-06-27 20:39 UTCGHSA enrichment
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-26 19:14 UTCVendor advisory
  40. 2026-06-26 19:14 UTCGHSA enrichment
  41. 2026-06-25 17:51 UTCEG score recompute
  42. 2026-06-25 17:48 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-9705?
CVE-2026-9705 is a medium vulnerability published on June 25, 2026. 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…
When was CVE-2026-9705 disclosed?
CVE-2026-9705 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9705 actively exploited?
CVE-2026-9705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9705?
CVE-2026-9705 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-9705?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9705, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9705

Explore →

Is Your Infrastructure Affected by CVE-2026-9705?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.