CVE-2026-40997
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% of all known CVEs
Summary
Spring Web Services integrated with Spring Security may expose detailed account state (e.g., locked or disabled user) to remote SOAP clients via exception messages or callback outcomes, instead of generic authentication errors. Affects versions 5.0.0-5.0.1, 4.1.0-4.1.3, 4.0.0-4.0.18, 3.1.0-3.1.8.
Risk Assessment
An attacker can distinguish valid accounts from invalid ones and infer their state, aiding social engineering or brute-force attacks.
Recommendation
Upgrade Spring Web Services to a patched version or configure generic authentication error responses.
Other vulnerabilities in Spring Web Services
See all- CVE-2026-41000Low
In Spring Web Services (versions 5.0.0-5.0.1, 4.1.0-4.1.3, 4.0.0-4.0.18, 3.1.0-3.1.8) the Wss4jSecurityInterceptor did not properly wire ReplayCache instances into RequestData, making replay protections ineffective for UsernameToken nonces, timestamps, and SAML.
- CVE-2026-40999High
When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying their safety.
- CVE-2026-40998High
Vulnerability in Spring Web Services (Jaxp13XPathTemplate) causes XPath expressions to be processed with the JDK's default configuration instead of Spring's hardened parser. This can lead to XXE (XML External Entity) attacks when processing untrusted XML data.
- CVE-2026-40996Medium
In Spring Web Services, Wss4jSecurityInterceptor defaults allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default. This allows acceptance of RSA PKCS#1 v1.5 (rsa-1_5) encrypted keys during WS-Security decryption unless explicitly reconfigured.
- CVE-2026-40995Medium
In Spring Web Services, X509AuthenticationProvider can issue a fully authenticated token when a certificate maps to UserDetails without applying standard account lifecycle checks (disabled, locked, expired, or credentials-expired accounts).
- CVE-2026-40994High
Wss4jSecurityInterceptor initialized its BSP compliance flag so that inbound validation disabled WSS4J BSP enforcement on RequestData. Services that validate WS-Security on the network could therefore accept messages that violate BSP rules, weakening protocol-level checks.
Original NVD description (English source)
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.