CVE-2026-1035

LOWNVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-01-21. NVD baseline CVSS 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.1Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.

CVSS v3
3.1
EG Score
3.1(medium)
EPSS
20.1%
KEV
Not listed

Published

January 21, 2026

Last Modified

April 15, 2026

References (4)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-142026-04-02redhat
redhatrhbk/keycloak-rhel92026-04-02redhat
mavenorg.keycloak:keycloak-services—ghsa

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (202 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-1035?
CVE-2026-1035 is a low vulnerability published on January 21, 2026. A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This…
When was CVE-2026-1035 disclosed?
CVE-2026-1035 was first published in the National Vulnerability Database on January 21, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1035 actively exploited?
CVE-2026-1035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-1035?
CVE-2026-1035 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-1035?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1035, 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-1035

Explore →

Is Your Infrastructure Affected by CVE-2026-1035?

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

Start Free Scan →Browse All CVEs