CVE-2026-40997 json
SOAP security faults leak Spring Security account state
published 4mo ago modified 2mo ago also GHSA-5x25-c2rf-f2jx , EUVD-2026-36207
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state.
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.
Patch / fix
- maven org.springframework.ws:spring-ws-security 4.1.4, 5.0.2
- Spring Spring Web Services 3.1.9, 4.0.19, 4.1.3.1, 5.0.1.1
Is CVE-2026-40997 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.ws:spring-ws-security | >=5.0.0, <5.0.2 >=4.1.0, <4.1.4 >=4.0.0, <=4.0.18 >=3.1.0, <=3.1.8 |
5.0.2 4.1.4 |
Affected products
- Spring Spring Web Services
Classification
- Weakness
-
- CWE-209 Generation of Error Message Containing Sensitive Information
References
Sources
- CVE List CVE-2026-40997
- GitHub Advisory GHSA-5x25-c2rf-f2jx
- NVD CVE-2026-40997
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.