CVE-2026-9704

HIGHNVD 8.86.8
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 8.8; sources differ by 2.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in Keycloak. An authenticated user with low privileges can exploit this vulnerability by sending an oversized subject_token JSON Web Token (JWT) to the TokenEndpoint. When the token exceeds a 4000-character limit, it is silently dropped, causing the system to fall back to client credentials. This allows the user to gain the permissions of the client's service account, leading to privilege escalation.

CVSS v3
8.8
EG Score
6.8(medium)
EPSS
24.3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 26, 2026

Advisory Details (2)

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

2481877 – (CVE-2026-9704) CVE-2026-9704 keycloak: Keycloak: Privilege escalation due to oversized subject_token JWT

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

cve-details

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-operator-bundle:26.6.4-22026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.6-62026-06-10redhat

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.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:31 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 23:51 UTCVendor advisory
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 00:00 UTCVendor advisory
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 02:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-07-01 10:49 UTCVendor advisory
Show 70 more
  1. 2026-07-01 10:49 UTCGHSA enrichment
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:23 UTCVendor advisory
  4. 2026-06-29 14:23 UTCGHSA enrichment
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 08:07 UTCVendor advisory
  8. 2026-06-28 08:07 UTCGHSA enrichment
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 06:02 UTCVendor advisory
  11. 2026-06-27 06:02 UTCGHSA enrichment
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 03:23 UTCVendor advisory
  14. 2026-06-26 03:23 UTCGHSA enrichment
  15. 2026-06-25 13:50 UTCEPSS rescore
  16. 2026-06-25 01:23 UTCVendor advisory
  17. 2026-06-25 01:23 UTCGHSA enrichment
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
  26. 2026-06-17 11:38 UTCVendor advisory
  27. 2026-06-17 11:38 UTCGHSA enrichment
  28. 2026-06-16 17:53 UTCEPSS rescore
  29. 2026-06-16 09:40 UTCVendor advisory
  30. 2026-06-16 09:39 UTCGHSA enrichment
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 06:58 UTCVendor advisory
  33. 2026-06-15 06:58 UTCGHSA enrichment
  34. 2026-06-14 23:18 UTCEPSS rescore
  35. 2026-06-14 04:58 UTCVendor advisory
  36. 2026-06-14 04:58 UTCGHSA enrichment
  37. 2026-06-13 23:00 UTCEPSS rescore
  38. 2026-06-13 02:58 UTCVendor advisory
  39. 2026-06-13 02:58 UTCGHSA enrichment
  40. 2026-06-12 23:12 UTCEPSS rescore
  41. 2026-06-12 23:12 UTCEPSS rescore
  42. 2026-06-12 00:59 UTCVendor advisory
  43. 2026-06-12 00:59 UTCGHSA enrichment
  44. 2026-06-11 14:00 UTCEPSS rescore
  45. 2026-06-10 23:00 UTCGHSA enrichment
  46. 2026-06-10 22:19 UTCEPSS rescore
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-09 21:01 UTCGHSA enrichment
  49. 2026-06-08 23:31 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  50. 2026-06-08 18:54 UTCGHSA enrichment
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-07 15:25 UTCEPSS rescore
  53. 2026-06-07 13:30 UTCGHSA enrichment
  54. 2026-06-06 13:47 UTCEPSS rescore
  55. 2026-06-06 11:30 UTCGHSA enrichment
  56. 2026-06-05 22:47 UTCEPSS rescore
  57. 2026-06-05 09:32 UTCGHSA enrichment
  58. 2026-06-05 06:10 UTCEPSS rescore
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-04 07:33 UTCGHSA enrichment
  61. 2026-06-03 05:34 UTCGHSA enrichment
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-02 03:35 UTCGHSA enrichment
  64. 2026-06-01 13:52 UTCEPSS rescore
  65. 2026-06-01 01:36 UTCGHSA enrichment
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 00:16 UTCEPSS rescore
  68. 2026-05-29 13:44 UTCEPSS rescore
  69. 2026-05-28 13:44 UTCEPSS rescore
  70. 2026-05-27 14:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-9704?
CVE-2026-9704 is a high vulnerability published on May 27, 2026. A flaw was found in Keycloak. An authenticated user with low privileges can exploit this vulnerability by sending an oversized subject_token JSON Web Token (JWT) to the TokenEndpoint. When the token exceeds a 4000-character limit, it is silently dropped, causing the system to fall back to client…
When was CVE-2026-9704 disclosed?
CVE-2026-9704 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9704 actively exploited?
CVE-2026-9704 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9704?
CVE-2026-9704 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.8.
How do I remediate CVE-2026-9704?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9704, 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-9704

Explore →

Is Your Infrastructure Affected by CVE-2026-9704?

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