Loading vulnerability…
CVE-2026-41000 is a replay-protection flaw in Spring Web Services' spring-ws-security integration with Apache WSS4J. Wss4jSecurityInterceptor did not consistently pass configured ReplayCache instances into WSS4J RequestData during validation. Consequently, validation-time anti-replay checks for UsernameToken nonces and creation timestamps, Timestamp elements, and certain SAML one-time-use assertions could be ineffective even when a replay cache was configured on the interceptor. Affected versions are Spring Web Services 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity replay-protection flaw in Spring Web Services' spring-ws-security component. Improper ReplayCache wiring in Wss4jSecurityInterceptor can render configured replay protections ineffective for UsernameToken nonces and timestamps, Timestamp elements, and some SAML one-time-use semantics.
A Spring vulnerability in the same release involving misconfiguration of the replay cache for UsernameToken nonce and timestamps.
Another Spring Web Services vulnerability mentioned only in passing; described here as UsernameToken replay issues.
A vulnerability in Spring Web Services where UsernameToken nonce/timestamp replay cache is never configured, potentially enabling replay attacks.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.