Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-41000

WSS4J validation does not use configured replay cache

Low3.7EPSS 0.22%
Published
Updated
Reserved
Assigned by
vmware

Description

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.

Scores

CVSS scores of CVE-2026-41000, by who scored it
Scored byCVSSScoreVector
vmwareCNA (assigner)3.1Low3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NVDNVD · Analyzed3.1Low3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.7.

Weakness

Affected products

  • Spring · Spring Web Services

    • affected 5.0.0 – < 5.0.1.1
    • affected 4.1.0 – < 4.1.3.1
    • affected 4.0.0 – < 4.0.19
    • affected 3.1.0 – < 3.1.9

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-41000 badge
[![CVE-2026-41000](https://trackcve.app/badge/CVE-2026-41000.svg)](https://trackcve.app/cve/CVE-2026-41000)

Record last updated .