Certificate revocation check can be bypassed when a message carries multiple XML signatures

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

Description

Wss4jSecurityInterceptor.verifyCertificateTrust() is the only place inbound WS-Security signing certificates are checked for revocation, but it only validated the first SIGN result found in the message. When an inbound message carries more than one XML signature, the certificates behind any additional signatures were never checked, so a message can pass validation even when signed with a revoked certificate, as long as another, valid signature is also present.

This affects deployments that validate inbound WS-Security signatures with Wss4jSecurityInterceptor with enableRevocation set, and accept messages that may carry more than one XML signature.

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