CVE-2026-59329

Information Exposure
Affects
Spring Security
in
Spring
No items found.
Versions
>=5.7.0 <=5.7.26, >=5.8.0 <=5.8.28, >=6.4.0 <=6.4.19, >=6.5.0 <=6.5.12, >=7.0.0 <=7.0.8, >=7.1.0 <=7.1.2

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Spring Security is a powerful and highly customizable authentication and access-control framework. It is the de-facto standard for securing Spring-based applications.

An information exposure vulnerability (CVE-2026-59329) has been identified in the reactive authentication support of Spring Security, which allows attackers to enumerate valid usernames by measuring how long authentication requests take. A login attempt for a username that does not exist returns measurably faster than one for an existing user with a wrong password.

Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.

This issue affects multiple versions of Spring Security.

Details

Module Info

Vulnerability Info

This Low-severity vulnerability is found in the org.springframework.security:spring-security-core package in multiple versions of Spring Security. It affects applications that authenticate with AbstractUserDetailsReactiveAuthenticationManager or a subclass such as UserDetailsRepositoryReactiveAuthenticationManager, which reactive (WebFlux) form login uses, and whose authentication endpoint an attacker can reach.

The reactive authenticate() method only invokes the configured PasswordEncoder after retrieveUser() emits a user:

return retrieveUser(username)
                .doOnNext(this.preAuthenticationChecks::check)
                .publishOn(this.scheduler)
                .filter((userDetails) -> this.passwordEncoder.matches(presentedPassword, userDetails.getPassword()))
                .switchIfEmpty(Mono.defer(() -> Mono.error(new BadCredentialsException("Invalid Credentials"))))
                ...

When the username does not exist, retrieveUser() (for UserDetailsRepositoryReactiveAuthenticationManager, userDetailsService.findByUsername(username)) completes empty or signals a UsernameNotFoundException. The chain then skips passwordEncoder.matches entirely and fails straight away, with a BadCredentialsException for an empty result or with the UsernameNotFoundException itself. Likewise, when the pre-authentication checks reject an existing account (locked, disabled or expired), the exception is thrown before any password comparison. Password encoders such as BCrypt are deliberately CPU-intensive, so a request for an unknown username finishes measurably faster than a request for a known username with an incorrect password. The blocking DaoAuthenticationProvider avoids this by running a dummy password match when the user is not found, but the reactive manager has no equivalent.

An unauthenticated attacker who can send login requests and time the responses can use this difference to tell valid usernames from invalid ones, then focus password guessing or credential-stuffing attacks on the accounts that exist. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N (3.7, Low): exploitation needs many timing samples, and only the existence of accounts is disclosed.

Mitigation

Only recent versions of Spring Security receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.

Users of the affected components should apply one of the following mitigations:

  • Upgrade to a currently supported version of Spring Security.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.

Credits

Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Low
ID
CVE-2026-59329
PROJECT Affected
Spring Security
Versions Affected
>=5.7.0 <=5.7.26, >=5.8.0 <=5.8.28, >=6.4.0 <=6.4.19, >=6.5.0 <=6.5.12, >=7.0.0 <=7.0.8, >=7.1.0 <=7.1.2
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Information Exposure
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.