CVE-2026-40996: VMware Spring Web Services insecure default in Wss4jSecurityInterceptor

CVE-2026-40996 · Severity: medium · CVSS 4.8 · Published 2026-06-11

Spring Web Services is a framework for building SOAP-based web services. A configuration default allows the system to accept weak RSA encryption algorithms for decrypting message keys, which cryptographic standards now recommend against. An attacker with network access could exploit this to decrypt inbound WS-Security messages or potentially forge signed messages, compromising the confidentiality and integrity of sensitive data exchanged via these web services.

Technologies: org.springframework.ws:spring-ws-security (Maven), VMware Spring Web Services. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-40996 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40996 being exploited in the wild.
How severe is CVE-2026-40996?
Medium severity, with a CVSS score of 4.8, published 11 June 2026.
Which products and versions are affected?
org.springframework.ws:spring-ws-security (Maven) ECOSYSTEM:introduced=5.0.0,fixed=5.0.2; VMware 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; VMware Web Services 5.0.0 through 5.0.1.
Is there a fix for CVE-2026-40996?
Yes. org.springframework.ws:spring-ws-security (Maven): upgrade to 5.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40996 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-40996?
Check whether you run org.springframework.ws:spring-ws-security (Maven), VMware Spring Web Services or VMware Web Services at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.ws:spring-ws-security (Maven): upgrade to 5.0.2 or later
    # set org.springframework.ws:spring-ws-security to 5.0.2 in your pom.xml or build.gradle

Technical details

This vulnerability exists in Spring Web Services' Wss4jSecurityInterceptor, which handles WS-Security processing for SOAP messages. The component defaulted the allowRSA15KeyTransportAlgorithm flag to true, overriding Apache WSS4J library's safer default for RequestData validation. This allows the framework to accept RSA PKCS#1 v1.5 (rsa-1_5) padding for encrypted key material during inbound message processing. RSA PKCS#1 v1.5 padding is cryptographically weaker than modern alternatives (OAEP) and subject to known padding oracle attacks. Exploitation requires network access to a vulnerable endpoint and knowledge of the public key, but no authentication is required. An attacker can mount decryption oracle attacks to recover encrypted key material or forge messages. Patches are available in versions 5.0.2 and 4.1.4; versions 4.0.0–4.0.18 and 3.1.0–3.1.8 are end-of-life without patches.

Affected products

  • Spring Web Services 5.0.0 through 5.0.1
  • Spring Web Services 4.1.0 through 4.1.3
  • Spring Web Services 4.0.0 through 4.0.18
  • Spring Web Services 3.1.0 through 3.1.8

Identifiers

  • CVE-2026-40996
  • GHSA-p7qj-2q5w-f9r7

Timeline

  • 2026-06-11: disclosed: Published to GitHub Advisory Database and NVD
  • 2026-06-11: patched: Fixes available in Spring Web Services 5.0.2 and 4.1.4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.