CVE-2026-40997: CWE-209: Generation of Error Message Containing Sensitive Information in Spring Spring Web Services
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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-40997) involves the generation of error messages containing sensitive information in Spring Web Services when integrated with Spring Security. Specifically, exception messages or callback outcomes may reveal detailed account states such as whether a user account is locked or disabled, instead of returning generic authentication errors. This behavior can be exploited by remote attackers to differentiate valid user accounts from invalid ones and to infer the lifecycle state of accounts. The affected versions are Spring Web Services 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. There is no vendor advisory or patch information available at this time, and the remediation level is unknown.
Potential Impact
The vulnerability allows remote attackers to gain information about user account states (e.g., locked or disabled) through error messages, which can aid in user enumeration and account reconnaissance. This information disclosure does not directly impact system integrity or availability but compromises confidentiality by leaking sensitive authentication-related details.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider implementing custom error handling to avoid exposing detailed account state information in error messages. Avoid revealing specific authentication failure reasons in responses to remote clients.
CVE-2026-40997: CWE-209: Generation of Error Message Containing Sensitive Information in Spring Spring Web Services
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.
CVSS v3.1
Score 5.3medium
Affected software
pkg:maven/org.springframework.ws/spring-ws-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-40997) involves the generation of error messages containing sensitive information in Spring Web Services when integrated with Spring Security. Specifically, exception messages or callback outcomes may reveal detailed account states such as whether a user account is locked or disabled, instead of returning generic authentication errors. This behavior can be exploited by remote attackers to differentiate valid user accounts from invalid ones and to infer the lifecycle state of accounts. The affected versions are Spring Web Services 3.1.0 through 3.1.8, 4.0.0 through 4.0.18, 4.1.0 through 4.1.3, and 5.0.0 through 5.0.1. There is no vendor advisory or patch information available at this time, and the remediation level is unknown.
Potential Impact
The vulnerability allows remote attackers to gain information about user account states (e.g., locked or disabled) through error messages, which can aid in user enumeration and account reconnaissance. This information disclosure does not directly impact system integrity or availability but compromises confidentiality by leaking sensitive authentication-related details.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider implementing custom error handling to avoid exposing detailed account state information in error messages. Avoid revealing specific authentication failure reasons in responses to remote clients.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:19:12.969Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2a59ba318757064921d3b6
Added to database: 6/11/2026, 6:46:18 AM
Last enriched: 6/11/2026, 7:01:59 AM
Last updated: 6/11/2026, 10:39:18 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.