5.3
Medium
CVE-2026-40997 Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or…
Description
Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Spring Web Services 5.0 | 5.0.0 → < 5.0.1.1 | 5.0.1.1 |
| Spring Web Services 4.1 | 4.1.0 → < 4.1.3.1 | 4.1.3.1 |
| Spring Web Services 4.0 | 4.0.0 → < 4.0.19 | 4.0.19 |
| Spring Web Services 3.1 | 3.1.0 → < 3.1.9 | 3.1.9 |
Other CVEs of Spring Web Services
The 8 CVEs of Spring Web Services →
CVE-2026-41000
Wss4jSecurityInterceptor did not consistently wire Apache WSS4J ReplayCache instances into RequestData for…
3.7
Low
CVE-2026-40999
When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound…
8.6
High
CVE-2026-40998
Jaxp13XPathTemplate evaluated XPath expressions for StreamSource and SAXSource inputs using a code path that parsed…
8.2
High
CVE-2026-40996
Wss4jSecurityInterceptor defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default…
4.8
Medium