CVE-2026-59349
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 SOAP and plain XML web services, providing message factories, endpoint mappings and client templates on top of the Spring Framework.
A denial of service vulnerability (CVE-2026-59349) has been identified in the SaajSoapMessageFactory, AxiomSoapMessageFactory and DomPoxMessageFactory classes of Spring Web Services, which allows unauthenticated attackers to exhaust server memory by sending an arbitrarily large message to any endpoint.
Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others.
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 High-severity vulnerability is found in the org.springframework.ws:spring-ws-core package in multiple versions of Spring Web Services. Every WebServiceMessageFactory that Spring Web Services provides builds an incoming message by handing the raw request InputStream straight to an XML or SAAJ parser. In SaajSoapMessageFactory, the stream is passed to the SAAJ MessageFactory, which reads and materializes the entire SOAP message in memory:
public SaajSoapMessage createWebServiceMessage(InputStream inputStream) throws IOException {
MimeHeaders mimeHeaders = parseMimeHeaders(inputStream);
try {
inputStream = checkForUtf8ByteOrderMark(inputStream);
SOAPMessage saajMessage = this.messageFactory.createMessage(mimeHeaders, inputStream);
saajMessage.getSOAPPart().getEnvelope();
...
}DomPoxMessageFactory does the same with a DOM DocumentBuilder, building the full document tree from the stream:
public DomPoxMessage createWebServiceMessage(InputStream inputStream) throws IOException {
try {
DocumentBuilder documentBuilder = this.documentBuilderFactory.newDocumentBuilder();
Document request = documentBuilder.parse(inputStream);
return new DomPoxMessage(request, createTransformer(), this.contentType);
}
...
}AxiomSoapMessageFactory, which ships in every affected line except 4.0.x, likewise passes the stream to its parser. None of these factories places any bound on the number of bytes consumed. An attacker who can reach any Spring Web Services endpoint can therefore send an arbitrarily large request body, and the server keeps reading and buffering it until heap memory is exhausted, making the service unavailable to legitimate users. No authentication or special configuration is required, because this is the default behavior of every message factory. The same factories are used on the client side to read responses, so a client talking to a malicious or compromised server is exposed in the same way.
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.
Credits
- Yu Bao from PayPal Cybersecurity Team (finder)