CVE-2026-40994: CWE-1188: Initialization of a Resource with an Insecure Default in Spring Spring Web Services
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.
AI Analysis
Technical Summary
The vulnerability CVE-2026-40994 in Spring Web Services arises from the Wss4jSecurityInterceptor initializing its BSP compliance flag in a way that disables enforcement of WS-I Basic Security Profile rules during inbound message validation. This misconfiguration allows WS-Security validating services to accept messages that violate BSP rules, thereby weakening protocol-level security checks. The affected versions include Spring Web Services 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. The CVSS 3.1 score is 8.2, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, limited confidentiality impact, high integrity impact, and no availability impact. No official patch or remediation level is provided in the available data.
Potential Impact
The vulnerability allows attackers to bypass WS-I Basic Security Profile enforcement in Spring Web Services, potentially permitting malformed or non-compliant WS-Security messages to be accepted by services that rely on this validation. This weakens protocol-level security checks and could lead to integrity violations of the processed messages. There is no indication of availability impact or known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor Spring's official advisories for updates. Until a fix is available, consider additional WS-Security validation controls or compensating controls to enforce BSP compliance externally if feasible.
CVE-2026-40994: CWE-1188: Initialization of a Resource with an Insecure Default in Spring Spring Web Services
Description
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.
CVSS v3.1
Score 8.2high
Affected software
pkg:maven/org.springframework.ws/spring-ws-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-40994 in Spring Web Services arises from the Wss4jSecurityInterceptor initializing its BSP compliance flag in a way that disables enforcement of WS-I Basic Security Profile rules during inbound message validation. This misconfiguration allows WS-Security validating services to accept messages that violate BSP rules, thereby weakening protocol-level security checks. The affected versions include Spring Web Services 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. The CVSS 3.1 score is 8.2, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, limited confidentiality impact, high integrity impact, and no availability impact. No official patch or remediation level is provided in the available data.
Potential Impact
The vulnerability allows attackers to bypass WS-I Basic Security Profile enforcement in Spring Web Services, potentially permitting malformed or non-compliant WS-Security messages to be accepted by services that rely on this validation. This weakens protocol-level security checks and could lead to integrity violations of the processed messages. There is no indication of availability impact or known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor Spring's official advisories for updates. Until a fix is available, consider additional WS-Security validation controls or compensating controls to enforce BSP compliance externally if feasible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:19:12.969Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2a59ba318757064921d3ad
Added to database: 06/11/2026, 06:46:18 UTC
Last enriched: 06/24/2026, 14:29:45 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 142
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.