Spring Web Services Denial of Service via Unbounded Incoming Message Size

HIGH | NOVEMBER 19, 2026 | CVE-2026-59349

Description

SaajSoapMessageFactory, AxiomSoapMessageFactory, and DomPoxMessageFactory read an incoming message's InputStream directly into the underlying XML parser without any bound on the number of bytes consumed. An attacker who can reach any endpoint can send an arbitrarily large message and exhaust server memory.

This affects every deployment: there is no configuration precondition, as this is the default behavior of every message factory Spring-WS provides.

Fixed versions apply a default maximum message size of 10MB, controllable via the maxMessageSize property on each factory.

Affected Spring Products and Versions

Spring Web Services:

  • 5.0.0 - 5.0.3
  • 4.1.0 - 4.1.4
  • 4.0.0 - 4.0.19
  • 3.1.9 and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
5.0.3.1Enterprise Support Only
5.0.4OSS
4.1.5Enterprise Support Only
4.0.20Enterprise Support Only
3.1.10Enterprise Support Only

If you cannot upgrade immediately, restrict the size of incoming requests before they reach Spring Web Services:

  • At a reverse proxy in front of the application, cap the request body size.
  • At the servlet container level, configure a maximum request/POST size.

Credit

The issue was identified and responsibly reported by Yu Bao from PayPal Cybersecurity Team.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all