Incorrect Implementation of Authentication Algorithm 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 applications- Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORKWS-17320712
- published12 Jun 2026
- disclosed10 Jun 2026
- creditUnknown
Introduced: 10 Jun 2026
NewCVE-2026-40995 (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 Incorrect Implementation of Authentication Algorithm via the X509AuthenticationProvider class in X509AuthenticationProvider.java. The provider issues a fully authenticated X509AuthenticationToken whenever a presented certificate maps to UserDetails, without applying Spring Security's standard UserDetailsChecker account lifecycle checks. The omission affects both users freshly resolved through X509AuthoritiesPopulator and entries returned from X509UserCache, so accounts that are disabled, locked, expired, or have expired credentials continue to authenticate when mutual TLS or certificate-based SOAP authentication is in use. An attacker who holds a still-valid client certificate mapped to such a deactivated account retains that account's access, gaining limited read and modify capability within the account's privileges over the network.