Quick answers
- Is CVE-2026-59276 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59276 being exploited in the wild.
- How severe is CVE-2026-59276?
- Medium severity, with a CVSS score of 5.9, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Security 5.7.0–5.8.27, 6.4.0–6.5.11, 7.0.0–7.1.0.
- Is there a fix for CVE-2026-59276?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59276 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59276?
- Check whether you run VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Multiple Spring Security components use String.equals() instead of a constant-time comparison function to verify security-sensitive values. The vulnerability allows attackers to exploit timing side-channels: String.equals() returns immediately upon finding the first mismatched character, making the comparison time proportional to the number of correct leading characters. This timing information can be used to systematically guess correct values (e.g., CSRF tokens, authentication strings) without triggering normal authentication failures. The issue affects Spring Security versions 5.7.0–5.8.27, 6.4.0–6.5.11, and 7.0.0–7.1.0.
Affected products
- VMware Spring Security 5.7.0–5.8.27, 6.4.0–6.5.11, 7.0.0–7.1.0
Timeline
- 2026-08-27: disclosed