CVE-2026-40996

Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default

Published Jun 11, 2026 CVSS 3.1 · 4.8 Medium EPSS < 1% KEV · Not listed
Description
Wss4jSecurityInterceptor defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default for validation RequestData. Inbound WS-Security decryption could therefore accept RSA PKCS#1 v1.5 (rsa-1_5) encrypted key material unless operators explicitly reconfigured the flag.

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

Inbound WS‑Security processing in Spring Web Services exposes a cryptographic weakness: the interceptor defaults to allow the RSA PKCS#1 v1.5 key transport algorithm. This weaker algorithm is vulnerable to padding oracle and other attacks, and the default reverts to the unsafe option instead of the safer default used by Apache WSS4J. An attacker could craft a message that uses the insecure algorithm to manipulate the encrypted key material or potentially gain unauthorized access to the protected payload.

Affected Systems

The vulnerability affects 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, and 3.1.0 through 3.1.8.

Risk and Exploitability

The CVSS score is 4.8, indicating low overall severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting low exploitation probability. The attack vector is network via inbound WS‑Security messages; it requires an attacker to send a crafted message that uses the RSA PKCS#1 v1.5 encrypted key. The default configuration makes exploitation easier, but the weakness is limited to systems directly accepting inbound WS‑Security traffic.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest Spring Web Services release that no longer defaults to the insecure algorithm.
  • If upgrading is not possible, configure the Wss4jSecurityInterceptor component to set allowRSA15KeyTransportAlgorithm to false.
  • Verify that inbound messages use a stronger key transport algorithm such as RSA‑OAEP or equivalent.

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-p7qj-2q5w-f9r7 Spring Web Services: Inbound WS-Security allows RSA PKCS#1 v1.5 key transport 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': 'no', '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 defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default for validation RequestData. Inbound WS-Security decryption could therefore accept RSA PKCS#1 v1.5 (rsa-1_5) encrypted key material unless operators explicitly reconfigured the flag. 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 Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default
Weaknesses CWE-327
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-327

    Use of a Broken or Risky Cryptographic Algorithm

Sources

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