https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2026-41000.htmlhttps://patchthecve.com/cve/CVE-2026-41000.htmlFri, 04 Sep 2026 18:14:58 +0000LOW 3.7: Wss4jSecurityInterceptor did not consistently wire Apache WSS4J ReplayCache instances into RequestData for validation-time checks. As a result, protections against replay of UsernameToken nonces and creation timestamps, Timestamp elements, and certain SAML one-time-use semantics could be ineffectivehttps://patchthecve.com/cve/CVE-2026-40999.htmlhttps://patchthecve.com/cve/CVE-2026-40999.htmlFri, 04 Sep 2026 18:18:26 +0000HIGH 8.6: When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to. Affectedhttps://patchthecve.com/cve/CVE-2026-40998.htmlhttps://patchthecve.com/cve/CVE-2026-40998.htmlFri, 04 Sep 2026 18:19:26 +0000HIGH 8.2: Jaxp13XPathTemplate evaluated XPath expressions for StreamSource and SAXSource inputs using a code path that parsed attacker-controlled XML with the JDK's default DocumentBuilderFactory behavior instead of Spring's hardened parser configuration. Applications that evaluate XPath against untrusted XMLhttps://patchthecve.com/cve/CVE-2026-40997.htmlhttps://patchthecve.com/cve/CVE-2026-40997.htmlFri, 04 Sep 2026 17:01:57 +0000MEDIUM 5.3: Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote athttps://patchthecve.com/cve/CVE-2026-40996.htmlhttps://patchthecve.com/cve/CVE-2026-40996.htmlFri, 04 Sep 2026 17:08:43 +0000MEDIUM 4.8: Wss4jSecurityInterceptor defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default for validation RequestData. Inbound WS-Security decryption could therefore accept RSA PKCS#1 v1.5 (rsa-1_5) encrypted key material unless operators explicitly reconfigured the flag. Ahttps://patchthecve.com/cve/CVE-2026-40995.htmlhttps://patchthecve.com/cve/CVE-2026-40995.htmlFri, 04 Sep 2026 17:10:23 +0000MEDIUM 5.4: X509AuthenticationProvider could issue a fully authenticated X509AuthenticationToken when a presented certificate mapped to UserDetails, without applying Spring Security's standard account lifecycle checks (disabled, locked, expired, or credentials-expired accounts). Affected versions: Spring Web Shttps://patchthecve.com/cve/CVE-2026-40994.htmlhttps://patchthecve.com/cve/CVE-2026-40994.htmlFri, 04 Sep 2026 17:11:51 +0000HIGH 8.2: Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) compliance flag so that inbound validation disabled WSS4J BSP enforcement on RequestData. Services that validate WS-Security on the network could therefore accept messages that violate BSP rules, weakening protocol-level chec