CVE-2026-9704

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 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
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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

Vendor Advisories for CVE-2026-9704(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel92026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.4-192026-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.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.keycloak:keycloak-server-spi-private10.0.0 ... 9.0.3 (167 versions)26.6.3—
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (227 versions)26.6.3—

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 9× in last 7d / 38× 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.

Showing the most recent 100 of 205 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 08:38 UTCEG score recompute
  4. 2026-09-14 08:38 UTCVendor advisory
  5. 2026-09-13 16:48 UTCEPSS rescore
  6. 2026-09-12 15:02 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:38 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-06 13:48 UTCEPSS rescore
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:18 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:42 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:31 UTCEG score recompute
  24. 2026-08-25 05:31 UTCVendor advisory
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 15:21 UTCEG score recompute
  2. 2026-08-23 15:21 UTCVendor advisory
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 20:42 UTCEG score recompute
  6. 2026-08-21 20:42 UTCVendor advisory
  7. 2026-08-20 22:56 UTCEPSS rescore
  8. 2026-08-20 22:37 UTCVendor advisory
  9. 2026-08-20 11:37 UTCEG score recompute
  10. 2026-08-20 11:37 UTCVendor advisory
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 09:19 UTCVendor advisory
  15. 2026-08-16 15:37 UTCEG score recompute
  16. 2026-08-16 15:37 UTCVendor advisory
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:52 UTCEG score recompute
  19. 2026-08-16 02:52 UTCVendor advisory
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 23:09 UTCVendor advisory
  23. 2026-08-14 12:19 UTCVendor advisory
  24. 2026-08-14 01:29 UTCEG score recompute
  25. 2026-08-14 01:29 UTCVendor advisory
  26. 2026-08-13 22:00 UTCEPSS rescore
  27. 2026-08-13 09:09 UTCVendor advisory
  28. 2026-08-12 22:19 UTCEG score recompute
  29. 2026-08-12 22:19 UTCVendor advisory
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-12 11:29 UTCVendor advisory
  32. 2026-08-12 00:27 UTCEG score recompute
  33. 2026-08-12 00:27 UTCVendor advisory
  34. 2026-08-11 13:43 UTCEPSS rescore
  35. 2026-08-11 13:36 UTCVendor advisory
  36. 2026-08-11 00:14 UTCEG score recompute
  37. 2026-08-11 00:14 UTCVendor advisory
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 06:18 UTCVendor advisory
  40. 2026-08-09 19:28 UTCEG score recompute
  41. 2026-08-09 19:28 UTCVendor advisory
  42. 2026-08-09 13:47 UTCEPSS rescore
  43. 2026-08-09 08:38 UTCVendor advisory
  44. 2026-08-08 21:48 UTCEG score recompute
  45. 2026-08-08 21:48 UTCVendor advisory
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 03:34 UTCVendor advisory
  48. 2026-08-07 16:44 UTCEG score recompute
  49. 2026-08-07 16:44 UTCVendor advisory
  50. 2026-08-07 16:30 UTCEPSS rescore
  51. 2026-08-07 05:54 UTCVendor advisory
  52. 2026-08-06 18:36 UTCEG score recompute
  53. 2026-08-06 18:36 UTCVendor advisory
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-06 07:45 UTCVendor advisory
  56. 2026-08-05 20:54 UTCEG score recompute
  57. 2026-08-05 20:54 UTCVendor advisory
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:39 UTCEPSS rescore
  61. 2026-08-04 03:25 UTCVendor advisory
  62. 2026-08-03 16:28 UTCEG score recompute
  63. 2026-08-03 16:28 UTCVendor advisory
  64. 2026-08-03 10:36 UTCEPSS rescore
  65. 2026-08-02 23:56 UTCVendor advisory
  66. 2026-08-02 13:06 UTCVendor advisory
  67. 2026-08-02 02:16 UTCVendor advisory
  68. 2026-08-01 15:26 UTCEG score recompute
  69. 2026-08-01 15:26 UTCVendor advisory
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-31 07:33 UTCEG score recompute
  72. 2026-07-31 07:33 UTCVendor advisory
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 15:40 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 0% probability of exploitation in the next 30 days, which ranks it in the top 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-9704?
CVE-2026-9704 has a CVSS v3 base score of 8.8 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs