CVE-2026-41000: WSS4J validation does not use configured replay cache
Spring · Spring Web Services
Vendor fix available · Affected: Spring Web Services · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 13% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Spring · Spring Web Servicesfrom 5.0.0 before 5.0.1.1; from 4.1.0 before 4.1.3.1; from 4.0.0 before 4.0.19; from 3.1.0 before 3.1.9
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2026-41000 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.