CVE-2026-40996: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in Spring Spring Web Services
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.
AI Analysis
Technical Summary
The vulnerability arises because the Wss4jSecurityInterceptor in Spring Web Services sets the allowRSA15KeyTransportAlgorithm flag to true by default, which permits the use of the RSA PKCS#1 v1.5 encryption algorithm for key transport during WS-Security decryption. This algorithm is considered broken or risky (CWE-327). Unless operators explicitly disable this flag, the system accepts RSA 1.5 encrypted key material, potentially weakening cryptographic security. The issue affects multiple versions of Spring Web Services from 3.1.0 up to 5.0.1. There is no vendor advisory or patch information provided, and no known exploits in the wild have been reported.
Potential Impact
The use of a broken or risky cryptographic algorithm (RSA PKCS#1 v1.5) for key transport in WS-Security decryption could reduce the cryptographic strength of the system, potentially allowing attackers to exploit weaknesses in the RSA 1.5 algorithm. The CVSS score of 4.8 indicates a medium severity impact with low confidentiality and integrity impact and no availability impact. However, no known exploits have been reported, and the vulnerability requires high attack complexity without privileges or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Operators should explicitly reconfigure the allowRSA15KeyTransportAlgorithm flag to false to disable acceptance of RSA PKCS#1 v1.5 encrypted key material. Until an official fix is available, this configuration change is the recommended mitigation to avoid using the risky cryptographic algorithm.
CVE-2026-40996: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in Spring Spring Web Services
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.
CVSS v3.1
Score 4.8medium
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 arises because the Wss4jSecurityInterceptor in Spring Web Services sets the allowRSA15KeyTransportAlgorithm flag to true by default, which permits the use of the RSA PKCS#1 v1.5 encryption algorithm for key transport during WS-Security decryption. This algorithm is considered broken or risky (CWE-327). Unless operators explicitly disable this flag, the system accepts RSA 1.5 encrypted key material, potentially weakening cryptographic security. The issue affects multiple versions of Spring Web Services from 3.1.0 up to 5.0.1. There is no vendor advisory or patch information provided, and no known exploits in the wild have been reported.
Potential Impact
The use of a broken or risky cryptographic algorithm (RSA PKCS#1 v1.5) for key transport in WS-Security decryption could reduce the cryptographic strength of the system, potentially allowing attackers to exploit weaknesses in the RSA 1.5 algorithm. The CVSS score of 4.8 indicates a medium severity impact with low confidentiality and integrity impact and no availability impact. However, no known exploits have been reported, and the vulnerability requires high attack complexity without privileges or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Operators should explicitly reconfigure the allowRSA15KeyTransportAlgorithm flag to false to disable acceptance of RSA PKCS#1 v1.5 encrypted key material. Until an official fix is available, this configuration change is the recommended mitigation to avoid using the risky cryptographic algorithm.
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: 6a2a59ba318757064921d3b3
Added to database: 6/11/2026, 6:46:18 AM
Last enriched: 6/11/2026, 7:02:08 AM
Last updated: 6/11/2026, 10:39:27 AM
Views: 9
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.