CVE-2026-40994: Wss4jSecurityInterceptor disables WS-I BSP validation by default
Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) 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.
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Enable the Wss4jSecurityInterceptor BSP compliance flag so inbound validation enforces WSS4J WS-I BSP checks on RequestData.
Wss4jSecurityInterceptor BSP compliance flag = true - Operational
Audit initialization of Wss4jSecurityInterceptor in applications using Spring Web Services (versions 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) and ensure the BSP compliance flag is set to enable BSP enforcement for inbound messages.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40994?
The severity of CVE-2026-40994 is rated high with a score of 8.2.
How do I fix CVE-2026-40994?
To fix CVE-2026-40994, ensure that WS-I BSP validation is enabled in the Wss4jSecurityInterceptor configuration.
What vulnerabilities does CVE-2026-40994 introduce?
CVE-2026-40994 can allow acceptance of messages that violate WS-I BSP rules, weakening protocol-level security checks.
Which software is affected by CVE-2026-40994?
CVE-2026-40994 affects the Spring Web Services framework.
When was CVE-2026-40994 published?
CVE-2026-40994 was published on June 11, 2026.