Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.springframework.ws:spring-ws-security

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.8MavenPublished

    Spring Web Services: Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default

    CVE-2026-40996 · GHSA-p7qj-2q5w-f9r7

    Affected
    • Maven org.springframework.ws:spring-ws-security >= 5.0.0, <= 5.0.1; >= 4.1.0, <= 4.1.3; >= 4.0.0, <= 4.0.18; >= 3.1.0, <= 3.1.8
    Fixed in
    4.1.45.0.2· Partial vendor fix
    Issue
    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-15) encrypted key material unless operators explicitly reconfigured the flag. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

    Recommended action: Upgrade to 5.0.2 or 4.1.4 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Low, CVSS 3.7MavenPublished

    Spring Web Services: WSS4J validation does not use configured replay cache

    CVE-2026-41000 · GHSA-8qq9-r6cc-qjv9

    Affected
    • Maven org.springframework.ws:spring-ws-security >= 5.0.0, <= 5.0.1; >= 4.1.0, <= 4.1.3; >= 4.0.0, <= 4.0.18; >= 3.1.0, <= 3.1.8
    Fixed in
    4.1.45.0.2· Partial vendor fix
    Issue
    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 ineffective even when operators configured a replay cache on the interceptor. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

    Recommended action: Upgrade to 5.0.2 or 4.1.4 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 5.4MavenPublished

    Spring Web Services: X.509 authentication bypasses Spring Security account checks

    CVE-2026-40995 · GHSA-6mfm-98wv-32wm

    Affected
    • Maven org.springframework.ws:spring-ws-security >= 5.0.0, <= 5.0.1; >= 4.1.0, <= 4.1.3; >= 4.0.0, <= 4.0.18; >= 3.1.0, <= 3.1.8
    Fixed in
    4.1.45.0.2· Partial vendor fix
    Issue
    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 Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

    Recommended action: Upgrade to 5.0.2 or 4.1.4 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 5.3MavenPublished

    Spring Web Services: SOAP security faults leak Spring Security account state

    CVE-2026-40997 · GHSA-5x25-c2rf-f2jx

    Affected
    • Maven org.springframework.ws:spring-ws-security >= 5.0.0, <= 5.0.1; >= 4.1.0, <= 4.1.3; >= 4.0.0, <= 4.0.18; >= 3.1.0, <= 3.1.8
    Fixed in
    4.1.45.0.2· Partial vendor fix
    Issue
    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 attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

    Recommended action: Upgrade to 5.0.2 or 4.1.4 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. High, CVSS 8.2MavenPublished

    Spring Web Services: Wss4jSecurityInterceptor disables WS-I BSP validation by default

    CVE-2026-40994 · GHSA-gg9r-wr4p-w63h

    Affected
    • Maven org.springframework.ws:spring-ws-security >= 5.0.0, <= 5.0.1; >= 4.1.0, <= 4.1.3; >= 4.0.0, <= 4.0.18; >= 3.1.0, <= 3.1.8
    Fixed in
    4.1.45.0.2· Partial vendor fix
    Issue
    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 checks. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

    Recommended action: Upgrade to 5.0.2 or 4.1.4 by release line; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →