CVE-2026-59276

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

Published Aug 27, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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

Analysis

AI-generated

Technical impact

Spring Security components use standard string equality for comparing sensitive values, which returns after detecting the first non‑matching character. This means the rejection time correlates with the number of matching leading characters. Based on the description, it is inferred that an attacker could measure response times to infer the correct value character by character, leaking credentials or tokens and enabling unauthorized access.

Affected Systems

The flaw exists in Spring Security for the following versions: 5.7.0 through 5.7.25, 5.8.0 through 5.8.27, 6.4.0 through 6.4.18, 6.5.0 through 6.5.11, 7.0.0 through 7.0.6, and 7.1.0. All deployments using these releases are vulnerable.

Risk and Exploitability

The CVSS score of 5.9 indicates medium severity. The EPSS score is less than 1%, and the vulnerability is not listed in CISA’s KEV catalog, so the likelihood of exploitation is unknown. The attack is likely performed remotely via authentication or token validation endpoints that compare user supplied values, requiring the attacker to observe response timing for each request. While each request yields partial information, repeated trials can recover the entire sensitive value.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Security to the latest patched release (e.g., 7.1.1 or later).
  • Replace any custom usage of String.equals() for sensitive comparisons with constant‑time comparison functions such as MessageDigest.isEqual.
  • Introduce network‑level timing mitigation, such as randomizing response times or applying rate limiting on authentication/token validation endpoints, to reduce timing side‑channel leakage.

Generated by OpenCVE AI on August 28, 2026 at 18:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Security
CPEs cpe:2.3:a:vmware:spring_security:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Security
Type Values Removed Values Added
Weaknesses CWE-465
Type Values Removed Values Added
Weaknesses CWE-208
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-465
Type Values Removed Values Added
First Time appeared Spring
Spring spring Security
Vendors & Products Spring
Spring spring Security
Type Values Removed Values Added
Description 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
Title Timing Attack via Non-Constant-Time Comparison of Sensitive Values
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-208

    Observable Timing Discrepancy

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 2:00 PM
Reserved
Jul 4, 2026, 6:13 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Sep 2, 2026, 4:45 PM
Severity
Moderate
Public date
Aug 27, 2026, 5:57 PM