CVE-2026-59370
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 focused on creating document-driven web services. It facilitates contract-first SOAP service development and provides WS-Security support for signing, encrypting and authenticating SOAP messages.
An information exposure vulnerability (CVE-2026-59370) has been identified in the WS-Security support of Spring Web Services, which allows unauthenticated attackers to learn from the SOAP fault returned to them which WS-Security check failed and why. Because the fault message varies with the cause, an attacker can also tell the failure modes of a submitted message apart.
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-security - 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-security
- 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-security package in multiple versions of Spring Web Services. Inbound WS-Security processing is performed by a subclass of AbstractWsSecurityInterceptor, such as Wss4jSecurityInterceptor. When validation of the security header of an incoming request fails, handleRequest catches the resulting WsSecurityValidationException and passes it to handleValidationException. If no exceptionResolver is configured, that method builds the SOAP 1.1 Client or SOAP 1.2 Sender fault returned to the sender from the message of the underlying exception:
protected boolean handleValidationException(WsSecurityValidationException ex, MessageContext messageContext) {
if (this.logger.isWarnEnabled()) {
this.logger.warn("Could not validate request: " + ex.getMessage());
}
if (this.exceptionResolver != null) {
this.exceptionResolver.resolveException(messageContext, null, ex);
}
else {
if (this.logger.isDebugEnabled()) {
this.logger.debug("No exception resolver present, creating basic soap fault");
}
SoapBody response = ((SoapMessage) messageContext.getResponse()).getSoapBody();
response.addClientOrSenderFault(ex.getMessage(), Locale.ENGLISH);
}
return false;
}The exception message describes which check failed and why, and the fault is sent before the sender is authenticated. An unauthenticated sender therefore receives the internal reason for the rejection in the fault string, and because that string differs from one cause to another, can submit crafted messages and use the responses to distinguish the failure modes of the security processing. Deployments are affected when an AbstractWsSecurityInterceptor subclass handles inbound WS-Security and no custom EndpointExceptionResolver replaces the fault built from the validation exception.
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.