Information Exposure Affecting org.springframework.ws:spring-ws-security package, versions [,4.1.4)[5.0.0-M1,5.0.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Information Exposure vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORKWS-17320569
- published12 Jun 2026
- disclosed10 Jun 2026
- creditUnknown
Introduced: 10 Jun 2026
NewCVE-2026-40997 (opens in a new tab)How to fix?
Upgrade org.springframework.ws:spring-ws-security to version 4.1.4, 5.0.2 or higher.
Overview
Affected versions of this package are vulnerable to Information Exposure due to the Spring Security integration paths in SpringSecurityUtils.checkUserValidity(), SpringSecurityPasswordValidationCallbackHandler, and X509AuthenticationProvider, which surface account status exceptions such as LockedException and DisabledException (with SpringSecurityUtils embedding full UserDetails content in exception messages) to remote SOAP clients instead of failing uniformly with a generic BadCredentialsException. A remote attacker submitting SOAP requests through the username-token, digest, or X.509 validation paths can distinguish valid accounts from invalid ones and infer account lifecycle state (locked, disabled, or expired), enabling user enumeration.