CVE-2026-40999: CWE-918: Server-Side Request Forgery (SSRF) in Spring Spring Web Services
When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to. 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
Spring Web Services versions 3.1.0 to 3.1.8, 4.0.0 to 4.0.18, 4.1.0 to 4.1.3, and 5.0.0 to 5.0.1 contain a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) identified as CVE-2026-40999. When WS-Addressing is configured with non-anonymous ReplyTo or FaultTo addresses, the framework may initiate outbound connections using WebServiceMessageSender instances to destinations derived directly from request headers without verifying their safety. This can allow an attacker to induce the server to make arbitrary HTTP requests to internal or external systems. The CVSS v3.1 base score is 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), indicating high severity with network attack vector, low attack complexity, no privileges or user interaction required, scope changed, and high confidentiality impact. No official remediation or patch information is currently provided.
Potential Impact
Successful exploitation allows an unauthenticated attacker to cause the affected Spring Web Services server to make arbitrary outbound HTTP requests to attacker-controlled or internal destinations. This can lead to unauthorized information disclosure from internal systems or services accessible only from the server, impacting confidentiality. There is no direct impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling WS-Addressing features that use non-anonymous ReplyTo or FaultTo addresses or implement network-level controls to restrict outbound connections from the affected service. Monitor vendor communications for updates on patches or official mitigations.
CVE-2026-40999: CWE-918: Server-Side Request Forgery (SSRF) in Spring Spring Web Services
Description
When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to. 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.6high
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
Spring Web Services versions 3.1.0 to 3.1.8, 4.0.0 to 4.0.18, 4.1.0 to 4.1.3, and 5.0.0 to 5.0.1 contain a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) identified as CVE-2026-40999. When WS-Addressing is configured with non-anonymous ReplyTo or FaultTo addresses, the framework may initiate outbound connections using WebServiceMessageSender instances to destinations derived directly from request headers without verifying their safety. This can allow an attacker to induce the server to make arbitrary HTTP requests to internal or external systems. The CVSS v3.1 base score is 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), indicating high severity with network attack vector, low attack complexity, no privileges or user interaction required, scope changed, and high confidentiality impact. No official remediation or patch information is currently provided.
Potential Impact
Successful exploitation allows an unauthenticated attacker to cause the affected Spring Web Services server to make arbitrary outbound HTTP requests to attacker-controlled or internal destinations. This can lead to unauthorized information disclosure from internal systems or services accessible only from the server, impacting confidentiality. There is no direct impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling WS-Addressing features that use non-anonymous ReplyTo or FaultTo addresses or implement network-level controls to restrict outbound connections from the affected service. Monitor vendor communications for updates on patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:19:12.970Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2a59ba318757064921d3bc
Added to database: 06/11/2026, 06:46:18 UTC
Last enriched: 06/24/2026, 14:30:29 UTC
Last updated: 07/30/2026, 08:52:01 UTC
Views: 106
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.