Spring Web Services Wss4jSecurityInterceptor BSP Validation Disabled by Default
CVE-2026-40994 affects Spring Web Services in configurations using Wss4jSecurityInterceptor for inbound WS-Security validation. The interceptor initialized its WS-I Basic Security Profile (BSP) compliance flag such that WSS4J BSP enforcement on RequestData was disabled during inbound validation. As a result, affected services could accept WS-Security messages that violate BSP rules, including rules around signatures and related WS-Security constructs, weakening protocol-level validation intended to enforce safe and interoperable message handling. Affected versions are Spring Web Services 5.0.0 through 5.0.1, 4.1.0 through 4.1.3, 4.0.0 through 4.0.18, and 3.1.0 through 3.1.8; unsupported versions may also be affected.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Spring Web Services where Wss4jSecurityInterceptor disables WSS4J BSP enforcement during inbound validation, allowing WS-Security messages that violate BSP rules to be accepted and weakening protocol-level security checks.
A vulnerability in Spring Web Services' Wss4jSecurityInterceptor where WS-I Basic Security Profile validation is disabled by default for inbound WS-Security validation, weakening protocol-level security checks and allowing acceptance of non-BSP-compliant messages.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.