CVE-2026-59352
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, built to facilitate contract-first SOAP service development. Its spring-ws-security module adds WS-Security support, including signing, signature validation and certificate trust checks through Apache WSS4J.
A signature forgery vulnerability (CVE-2026-59352) has been identified in the Wss4jSecurityInterceptor of Spring Web Services, which allows attackers to get an inbound SOAP message accepted even though one of its XML signatures was made with a revoked certificate, as long as another valid signature is also present in the message.
Per OWASP: Confirmation of the user's identity, authentication, and session management is critical to protect against authentication-related attacks.
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: >=5.0.0 <=5.0.3, >=4.1.0 <=4.1.4, >=4.0.0 <=4.0.19, <=3.1.9
- 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. When Wss4jSecurityInterceptor validates an inbound message, verifyCertificateTrust() is the only place where the signing certificates are checked for revocation when enableRevocation is set. The method only looks at the first WSConstants.SIGN result that WSS4J produced for the message:
protected void verifyCertificateTrust(WSHandlerResult result) throws WSSecurityException {
List<WSSecurityEngineResult> results = result.getActionResults().get(WSConstants.SIGN);
if (!CollectionUtils.isEmpty(results)) {
WSSecurityEngineResult actionResult = results.get(0);
X509Certificate returnCert = (X509Certificate) actionResult
.get(WSSecurityEngineResult.TAG_X509_CERTIFICATE);
Credential credential = new Credential();
credential.setCertificates(new X509Certificate[] { returnCert });
RequestData requestData = new RequestData();
requestData.setSigVerCrypto(this.validationSignatureCrypto);
requestData.setEnableRevocation(this.enableRevocation);
requestData.setSubjectCertConstraints(this.signatureSubjectDnPatterns);
Validator validator = (this.wssConfig != null) ? this.wssConfig.getValidator(WSConstants.SIGNATURE) : null;
if (validator == null) {
validator = new SignatureTrustValidator();
}
validator.validate(credential, requestData);
}
}A WS-Security header can carry more than one XML signature, and WSS4J records one SIGN result per signature. Only the certificate behind the first result is passed to SignatureTrustValidator with revocation checking enabled. The certificates behind every other signature are never checked for revocation. An attacker who holds the private key of a revoked certificate can therefore add a signature made with that key to a message that also carries a valid signature, and the interceptor accepts the message along with the content covered by the revoked signer. Deployments are exposed when they validate inbound WS-Security signatures with Wss4jSecurityInterceptor with enableRevocation set and accept messages that may carry more than one XML signature.
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.