CVE-2026-40997: Several Spring WS integration paths with Spring Security could surface detailed account state (for example loc
CVE-2026-40997 is a medium-severity flaw (CVSS 5.3) affecting spring web services. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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;
Why this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 70%) |
| CISA exploited list | No |
| Weakness | CWE-209 |
| Published | 2026-06-11 |
| Last modified | 2026-09-04 |
Last updated 2026-09-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-40997?
spring web services: upgrade to 3.1.9, 4.0.19, 4.1.3.1, 5.0.1.1. Exact commands for each OS are on this page.
Is CVE-2026-40997 being exploited?
CVE-2026-40997 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-40997 affect?
CVE-2026-40997 affects spring web services. Severity is medium (CVSS 5.3). 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 ge
How urgent is CVE-2026-40997?
Priority 31/100. Remotely exploitable, no login, no user action
Related CVEs
- CVE-2026-40998 HIGH 8.2 UPGRADE Jaxp13XPathTemplate evaluated XPath expressions for StreamSource and SAXSource inputs using a code path that p
- CVE-2026-40999 HIGH 8.6 UPGRADE When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound co
- CVE-2026-41000 LOW 3.7 UPGRADE Wss4jSecurityInterceptor did not consistently wire Apache WSS4J ReplayCache instances into RequestData for val
- CVE-2026-40994 HIGH 8.2 UPGRADE Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) compliance flag so that inbound val
- CVE-2026-40995 MEDIUM 5.4 UPGRADE X509AuthenticationProvider could issue a fully authenticated X509AuthenticationToken when a presented certific