Skip to main content
VulnerabilityPublished Updated

CVE-2026-41000: Spring Web Services · Authentication Bypass by Capture-replay

Affects Spring Web ServicesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low · fixed in 5.0.1.1 : update Spring Web Services when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.1.1, 4.1.3.1, 4.0.19 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Spring Web Services to 5.0.1.1, 4.1.3.1, 4.0.19 or 3.1.9.

Affected software

ProductAffectedFixed in
SpringSpring Web ServicesAffected
  • >=5.0.0 <5.0.1.1
Fixed in
  • 5.0.1.1
SpringSpring Web ServicesAffected
  • >=4.1.0 <4.1.3.1
Fixed in
  • 4.1.3.1
SpringSpring Web ServicesAffected
  • >=4.0.0 <4.0.19
Fixed in
  • 4.0.19
SpringSpring Web ServicesAffected
  • >=3.1.0 <3.1.9
Fixed in
  • 3.1.9

AI-suggested

If you cannot patch yet, carefully review configurations of Wss4jSecurityInterceptor and consider additional compensating controls to detect or prevent replay attacks.

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.

References

Community reviews

Loading reviews…