Spring Security Reactive Authentication Timing Attack Enables Username Enumeration

LOW | NOVEMBER 19, 2026 | CVE-2026-59329

Description

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 Spring Products and Versions

Spring Security:

  • 7.1.0 - 7.1.2
  • 7.0.0 - 7.0.8
  • 6.5.0 - 6.5.12
  • 6.4.0 - 6.4.19
  • 5.8.0 - 5.8.28
  • 5.7.0 - 5.7.26

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
7.1.3OSS
7.1.2.1Enterprise Support Only
7.0.9OSS
7.0.8.1Enterprise Support Only
6.5.13Enterprise Support Only
6.4.20Enterprise Support Only
5.8.29Enterprise Support Only
5.7.27Enterprise Support Only

No further mitigation steps are necessary.

Credit

This issue was identified and responsibly reported by waydeshi and emmaw96.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all