CVE-2026-41000

WSS4J validation does not use configured replay cache

LOW

3.7

CVSS Score

Published: June 11, 2026 at 05:04 AM UTC

Updated: September 4, 2026 at 06:26 PM UTC

2 products affected across 2 vendorsSpring Web ServicesSpring Web Services

Using Spring Web Services by Spring?

Get instant alerts when new vulnerabilities affect Spring Web Services - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

LOW3.7

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spring Web Services · Broadcom

95%

v < 3.1.94.0.0 ≤ v < 4.0.194.1.0 ≤ v < 4.1.3.15.0.0 ≤ v < 5.0.1.1

Affected range stops below 3.1.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.0.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.1.3.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.0.1.1, so it looks safe — our inference, not a vendor statement

Spring Web Services · Spring

60%

3.1.0 ≤ v < 3.1.94.0.0 ≤ v < 4.0.194.1.0 ≤ v < 4.1.3.15.0.0 ≤ v < 5.0.1.13.1.0 4.0.0 4.1.0 5.0.0

Affected range stops below 3.1.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.0.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.1.3.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.0.1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://spring.io/security/cve-2026-41000

References (1)

Vendor AdvisoryMitigation

Source: cverecord

https://spring.io/security/cve-2026-41000

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.7LOWvmware

Attack Vector: NETWORK
Complexity: HIGH
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-294

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card