Spring Web Services: Initialization of a Resource with an Insecure Default
CVE-2026-40994 is a high-severity initialization of a resource with an insecure default vulnerability in Spring Web Services from Spring, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 5.0.1.1, 4.1.3.1, 4.0.19 as the first without the flaw, so updating Spring Web Services to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Spring Web Services to 5.0.1.1 or 4.1.3.1 or 4.0.19 or 3.1.9, whichever matches your release line, or a later version.
- Read the advisory on spring.io for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Spring | Spring Web Services | 5.0.0 up to, but not including, 5.0.1.1; 4.1.0 up to, but not including, 4.1.3.1; 4.0.0 up to, but not including, 4.0.19; 3.1.0 up to, but not including, 3.1.9 | 5.0.1.1, 4.1.3.1, 4.0.19, 3.1.9 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. Scored by CNA (vmware.com).
Official description
Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) compliance flag so that inbound validation disabled WSS4J BSP enforcement on RequestData. Services that validate WS-Security on the network could therefore accept messages that violate BSP rules, weakening protocol-level checks. 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Initialization of a Resource with an Insecure Default
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
More Initialization of a Resource with an Insecure Default vulnerabilities (CWE-1188)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- spring.io/security/cve-2026-40994Mitigation
Other vulnerabilities in Spring Web Services
- 8.6 High severity
- 8.2 High severity
Recent Initialization of a Resource with an Insecure Default vulnerabilities
- 8.6 High severity
- 7.5 High severity
- 7.4 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.7 High severity
Spotted an error? Tell us.