Insecure Defaults 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-17320710
- published12 Jun 2026
- disclosed10 Jun 2026
- creditUnknown
Introduced: 10 Jun 2026
NewCVE-2026-40994 (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 Insecure Defaults due to the Wss4jSecurityInterceptor class in Wss4jSecurityInterceptor.java initializing its bspCompliant flag to false, so inbound validation always calls RequestData.setDisableBSPEnforcement(true) and disables WSS4J's WS-I Basic Security Profile checks, contradicting the documented secure default of the setBspCompliant setter. A remote, unauthenticated attacker can send SOAP messages that violate BSP rules around signatures and related constructs to a service that uses the interceptor for inbound WS-Security validation, weakening defenses against non-standard transforms and signature-related abuse.
Workaround
This can be mitigated by enabling BSP compliance explicitly by calling the setBspCompliant setter method with true as the argument.