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
CVE-2026-59276
Score 5.9 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026Timing Attack via Non-Constant-Time Comparison of Sensitive Values
https://spring.io/security/cve-2026-59276Vendor 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 12× in last 7d / 12× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:00 UTCEG score recompute
- 2026-08-29 19:00 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:03 UTCGHSA enrichment
- 2026-08-28 16:41 UTCEG score recompute
- 2026-08-28 16:40 UTCGHSA enrichment
- 2026-08-28 15:42 UTCEG score recompute
- 2026-08-28 15:42 UTCGHSA enrichment
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:16 UTCEG score recompute
- 2026-08-27 20:13 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59276?
When was CVE-2026-59276 disclosed?
Is CVE-2026-59276 actively exploited?
What is the CVSS score of CVE-2026-59276?
How do I remediate CVE-2026-59276?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59276
Is Your Infrastructure Affected by CVE-2026-59276?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.