CVE-2026-59276

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 5.9; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Several components in Spring Security compare security-sensitive values using standard string equality (String.equals()) rather than a constant-time comparison. Because String.equals() returns as soon as it finds a differing character, the time taken to reject an incorrect value is proportional to the number of leading characters that match the expected value. Spring Security 7.1.0 Spring Security 7.0.0 - 7.0.6 Spring Security 6.5.0 - 6.5.11 Spring Security 6.4.0 - 6.4.18 Spring Security 5.8.0 - 5.8.27 Spring Security 5.7.0 - 5.7.25

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 2, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

Timing Attack via Non-Constant-Time Comparison of Sensitive Values

https://spring.io/security/cve-2026-59276

Vendor Advisories for CVE-2026-59276(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59276?
CVE-2026-59276 is a medium vulnerability published on August 27, 2026. Several components in Spring Security compare security-sensitive values using standard string equality (String.equals()) rather than a constant-time comparison. Because String.equals() returns as soon as it finds a differing character, the time taken to reject an incorrect value is proportional to…
When was CVE-2026-59276 disclosed?
CVE-2026-59276 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59276 actively exploited?
CVE-2026-59276 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 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59276?
CVE-2026-59276 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-59276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59276, 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-59276

Explore →

Is Your Infrastructure Affected by CVE-2026-59276?

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