CVE Watchtower

CVE-2026-59329Spring Security

Spring

Vulnerability Summary

Spring Security Reactive Authentication Timing Attack Enables Username Enumeration. Spring Security's reactive authentication support, AbstractUserDetailsReactiveAuthenticationManager and UserDetailsRepositoryReactiveAuthenticationManager, do not invoke the configured PasswordEncoder when a submitted username cannot be found, unlike its blocking counterpart DaoAuthenticationProvider. Because password encoding is deliberately CPU-intensive, the response time for a nonexistent username is measurably shorter than for a valid username with an incorrect password. Preconditions: The application authenticates using AbstractUserDetailsReactiveAuthenticationManager or a subclass, such as UserDetailsRepositoryReactiveAuthenticationManager (used by reactive .formLogin()). The authentication endpoint is reachable by the attacker. An unauthenticated attacker who can measure authentication response times can use this difference to enumerate valid usernames. Affected artifact: org.springframework.security:spring-security-core.
Severity Level
LOW(3.7)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 3.7 (LOW)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Spring Security 7.1.0 through 7.1.2
  • Spring Security 7.0.0 through 7.0.8
  • Spring Security 6.5.0 through 6.5.12
  • Spring Security 6.4.0 through 6.4.19
  • Spring Security 5.8.0 through 5.8.28
  • Spring Security 5.7.0 through 5.7.26
Patched Versions
  • Spring Security 7.1.3 (open source)
  • Spring Security 7.0.9 (open source)
  • Spring Security 7.1.2.1 (commercial support only)
  • Spring Security 7.0.8.1 (commercial support only)
  • Spring Security 6.5.13 (commercial support only)
  • Spring Security 6.4.20 (commercial support only)
  • Spring Security 5.8.29 (commercial support only)
  • Spring Security 5.7.27 (commercial support only)

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Spring Security and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring Security CVEsYou are reading CVE-2026-59329. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Security CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC