Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-06-11. a secondary CVSS source baseline 3.7; sources differ by 0.0.
A fix is available — apply it.
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.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
June 11, 2026
September 4, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.springframework.ws:spring-ws-security | 3.1.0 ... 3.1.8 (9 versions) |
| — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 153 total refreshes for this CVE.
Maven:org.springframework.ws:spring-ws-security
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41000
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.