CVE-2026-59350
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Web Services (Spring-WS) is a Spring project for building contract-first, document-driven SOAP web services, with support for WS-Addressing and WS-Security.
An information exposure vulnerability (CVE-2026-59350) has been identified in the WS-Addressing support of Spring Web Services, which causes responses that were meant to be signed or encrypted to be sent in cleartext to a caller-supplied reply address. When a caller supplies a non-anonymous wsa:ReplyTo or wsa:FaultTo address, the out-of-band reply is sent before a response-securing interceptor such as Wss4jSecurityInterceptor can process it.
Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
This issue affects multiple versions of Spring Web Services.
Details
Module Info
- Product: Spring Web Services
- Affected packages:
org.springframework.ws:spring-ws-core - Affected versions: <=3.1.9, >=4.0.0 <=4.0.19, >=4.1.0 <=4.1.4, >=5.0.0 <=5.0.3
- GitHub repository: https://github.com/spring-projects/spring-ws
- Published packages: https://central.sonatype.com/artifact/org.springframework.ws/spring-ws-core
- Package manager: Maven
- Fixed in:
- OSS Spring Web Services 5.0.4
- NES for Spring Web Services
Vulnerability Info
This Medium-severity vulnerability is found in the org.springframework.ws:spring-ws-core package in multiple versions of Spring Web Services.
The issue affects deployments where an AbstractAddressingEndpointMapping subclass is configured with one or more WebServiceMessageSender instances for out-of-band replies, a response-securing interceptor (such as Wss4jSecurityInterceptor with response signing or encryption enabled) is registered as a pre-interceptor on that mapping, and the service accepts a non-anonymous wsa:ReplyTo or wsa:FaultTo address from callers whose responses should be protected.
The endpoint mapping places its pre-interceptors before the AddressingEndpointInterceptor in the interceptor chain. MessageDispatcher runs handleResponse and handleFault over that chain in reverse order and stops at the first interceptor that returns false, so the security interceptor is expected to process the response last. In AddressingEndpointInterceptor, however, a non-anonymous reply address causes the response to be sent out-of-band immediately, after which the method returns false:
private boolean handleResponseOrFault(MessageContext messageContext, boolean isFault) throws Exception {
...
this.version.addAddressingHeaders(reply, replyMap);
if (handleAnonymousAddress(messageContext, replyEpr)) {
return true;
}
else {
sendOutOfBand(messageContext, replyEpr, () -> { ... });
return false;
}
}sendOutOfBand opens a connection to the caller-supplied address and calls connection.send(messageContext.getResponse()) with the response as it stands at that point. Because false is then returned, the reverse walk ends before the lower-index security interceptor runs, so the response is never signed or encrypted. A response that was meant to be protected by WS-Security is therefore transmitted in cleartext to the wsa:ReplyTo or wsa:FaultTo address, where it can be read by that endpoint or by anyone observing the connection.
Mitigation
Only recent versions of Spring Web Services receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a currently supported version of Spring Web Services.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.