WS-Security faults disclose why validation of a request failed

MEDIUM | NOVEMBER 19, 2026 | CVE-2026-59370

Description

When validation of an inbound WS-Security header failed, the SOAP fault returned to the sender used the message of the underlying exception as its fault string, telling an unauthenticated sender which check failed and why. Because that message varies with the cause, a sender can also distinguish the failure modes of a message it submitted.

This issue only affects deployments where all the following are true:

  • Inbound WS-Security processing is performed by an AbstractWsSecurityInterceptor subclass, such as Wss4jSecurityInterceptor.
  • No custom EndpointExceptionResolver replaces the fault string built from the validation exception.

Fixed versions return the same fault string, Security processing failed, whatever the failure, and log the details instead. A client relying on the previous fault string to tell failures apart will no longer be able to. Configure an exceptionResolver to take over building the fault.

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

No further mitigation steps are necessary.

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