CVE-2026-40997: Spring Web Services · Generation of Error Message Containing Sensitive Information
Affects Spring Web ServicesSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 5.0.1.1 : update Spring Web Services when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% 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:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 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
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring Web Services | Affected
| Fixed in
|
| SpringSpring Web Services | Affected
| Fixed in
|
| SpringSpring Web Services | Affected
| Fixed in
|
| SpringSpring Web Services | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, consider configuring the application to suppress detailed error messages in SOAP responses or customize error handling to avoid revealing sensitive account state information.
Description
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.