3.7
CVE-2026-41000
- EPSS 0.22%
- Veröffentlicht 11.06.2026 05:04:24
- Zuletzt bearbeitet 04.09.2026 18:14:58
- Erkennungen
WSS4J validation does not use configured replay cache
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.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Broadcom ≫ Spring Web Services Version < 3.1.9
Broadcom ≫ Spring Web Services Version >= 4.0.0 < 4.0.19
Broadcom ≫ Spring Web Services Version >= 4.1.0 < 4.1.3.1
Broadcom ≫ Spring Web Services Version >= 5.0.0 < 5.0.1.1
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.22% | 0.127 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| VMware | 3.7 | 2.2 | 1.4 |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
|
CWE-294 Authentication Bypass by Capture-replay
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
https://spring.io/security/cve-2026-41000