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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-41000
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 18:56 UTC · Revision 1
Source evidence
WSS4J validation does not use configured replay cache
core-osv · Original sourcePublished 11 Jun 2026, 05:04 UTC
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.
osv:CVE-2026-41000
Complete source record
{
"id": "550d5deabbd44102274bd9d4ef3f3b0fefe823b138fcdfe5f7ea416444653d67",
"url": "https://osv.dev/vulnerability/CVE-2026-41000",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "WSS4J validation does not use configured replay cache",
"summary": "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.",
"evidence": "osv:CVE-2026-41000",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-41000",
"aliases": [
"CVE-2026-41000",
"GHSA-8qq9-r6cc-qjv9"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/spring-projects/spring-ws",
"type": "GIT",
"events": [
{
"introduced": "03e870960cc6f5b591bf16d3ad3897f0aa452cc7"
},
{
"last_affected": "bce4cbc3e388d270bca1593970637e2d58076565"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "3.1.0"
},
{
"last_affected": "3.1.8"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v3.1.8",
"v3.1.7",
"v3.1.6",
"v3.1.5",
"v3.1.4",
"v3.1.3",
"v3.1.2",
"v3.1.1",
"v3.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-41000.json"
}
}
],
"modified": "2026-10-28T02:30:38.501509425Z",
"provider": "osv",
"references": [
"https://spring.io/security/cve-2026-41000",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41000.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-41000"
],
"provider_metadata": {
"cwe_ids": [
"CWE-294"
],
"cna_assigner": "vmware",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.1.1"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.3.1"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.19"
},
{
"introduced": "3.1.0"
},
{
"fixed": "3.1.9"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41000.json"
}
},
"related_cves": [
{
"value": "CVE-2026-41000",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505915,
"published_at": "2026-06-11T05:04:24.413+00:00"
}