CVE-2026-40994

Wss4jSecurityInterceptor disables WS-I BSP validation by default

Published Jun 11, 2026 CVSS 3.1 · 8.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Wss4jSecurityInterceptor incorrectly initializes its BSP compliance flag, disabling WSS4J Basic Security Profile enforcement on inbound requests. Because of this, services that rely on WS‑Security and expect strict BSP validation may accept messages that violate protocol rules, weakening security controls. This gap can allow attackers to craft messages that bypass validation, potentially leading to unauthorized actions or data compromise. The weakness is classified as CWE‑1188.

Affected Systems

Spring Web Services (Spring:Spring Web Services) is affected. Affected versions include 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.

Risk and Exploitability

The CVSS score is 8.2, indicating a high severity. The EPSS score is not available, making it unclear how often the vulnerability is actively exploited, but the problem can be mitigated if a patch is applied. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the attacker can exploit the disabled BSP validation by sending crafted SOAP messages that violate protocol rules, potentially to gain a foothold or perform unauthorized operations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Spring Web Services version that contains a fix for the BSP validation issue.
  • If an upgrade cannot be performed immediately, enable explicit BSP validation on inbound requests through configuration or by adding a custom interceptor.
  • Review and strengthen any custom WS‑Security validation logic to enforce protocol rules manually.

Generated by OpenCVE AI on June 11, 2026 at 07:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gg9r-wr4p-w63h Spring Web Services: Wss4jSecurityInterceptor disables WS-I BSP validation by default
References
History
Type Values Removed Values Added
First Time appeared Broadcom
Broadcom spring Web Services
CPEs cpe:2.3:a:broadcom:spring_web_services:*:*:*:*:*:*:*:*
Vendors & Products Broadcom
Broadcom spring Web Services
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Web Services
Vendors & Products Spring
Spring spring Web Services
Type Values Removed Values Added
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.
Title Wss4jSecurityInterceptor disables WS-I BSP validation by default
Weaknesses CWE-1188
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jun 23, 2026, 7:47 PM
Reserved
Apr 16, 2026, 2:19 AM
Status
Analyzed
Published
Jun 11, 2026, 7:16 AM
Modified
Sep 4, 2026, 5:11 PM