Vmware Spring Boot up to 4.0.5 PID File ApplicationPidFileWriter link following
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Vmware Spring Boot up to 2.7.32/3.3.18/3.4.15/3.5.13/4.0.5. It has been rated as critical. The impacted element is the function ApplicationPidFileWriter of the component PID File Handler. This manipulation causes link following.
This vulnerability is registered as CVE-2026-40977. The attack needs to be launched locally. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability has been found in Vmware Spring Boot up to 2.7.32/3.3.18/3.4.15/3.5.13/4.0.5 and classified as problematic. Affected by this vulnerability is the function ApplicationPidFileWriter of the component PID File Handler. The manipulation with an unknown input leads to a link following vulnerability. The CWE definition for the vulnerability is CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. As an impact it is known to affect integrity, and availability. The summary by CVE is:
When an application is configured to use `ApplicationPidFileWriter`, a local attacker with write access to the PID file's location can corrupt one file on the host each time the application is started. Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); PID file / symlink behavior (`ApplicationPidFileWriter`). Versions that are no longer supported are also affected per vendor advisory.
The advisory is shared at spring.io. This vulnerability is known as CVE-2026-40977 since 04/16/2026. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 311001 (Linux Distros Unpatched Vulnerability : CVE-2026-40977), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.7.33, 3.3.19, 3.4.16, 3.5.14 or 4.0.6 eliminates this vulnerability.
The vulnerability is also documented in the databases at CNNVD (CNNVD-202604-5558), Tenable (311001) and CERT Bund (WID-SEC-2026-1263). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Red Hat Enterprise Linux
- VMware Tanzu Spring Boot
- HCL Commerce
- Red Hat OpenShift
Product
Vendor
Name
Version
- 2.7.0
- 2.7.1
- 2.7.2
- 2.7.3
- 2.7.4
- 2.7.5
- 2.7.6
- 2.7.7
- 2.7.8
- 2.7.9
- 2.7.10
- 2.7.11
- 2.7.12
- 2.7.13
- 2.7.14
- 2.7.15
- 2.7.16
- 2.7.17
- 2.7.18
- 2.7.19
- 2.7.20
- 2.7.21
- 2.7.22
- 2.7.23
- 2.7.24
- 2.7.25
- 2.7.26
- 2.7.27
- 2.7.28
- 2.7.29
- 2.7.30
- 2.7.31
- 2.7.32
- 3.3.0
- 3.3.1
- 3.3.2
- 3.3.3
- 3.3.4
- 3.3.5
- 3.3.6
- 3.3.7
- 3.3.8
- 3.3.9
- 3.3.10
- 3.3.11
- 3.3.12
- 3.3.13
- 3.3.14
- 3.3.15
- 3.3.16
- 3.3.17
- 3.3.18
- 3.4.0
- 3.4.1
- 3.4.2
- 3.4.3
- 3.4.4
- 3.4.5
- 3.4.6
- 3.4.7
- 3.4.8
- 3.4.9
- 3.4.10
- 3.4.11
- 3.4.12
- 3.4.13
- 3.4.14
- 3.4.15
- 3.5.0
- 3.5.1
- 3.5.2
- 3.5.3
- 3.5.4
- 3.5.5
- 3.5.6
- 3.5.7
- 3.5.8
- 3.5.9
- 3.5.10
- 3.5.11
- 3.5.12
- 3.5.13
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.0.5
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 3.0
VulDB Temp Score: 2.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.7
CNA Vector (vmware): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Link followingCWE: CWE-59
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 311001
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-40977
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Spring Boot 2.7.33/3.3.19/3.4.16/3.5.14/4.0.6
Timeline
04/16/2026 CVE reserved04/28/2026 Advisory disclosed
04/28/2026 VulDB entry created
06/04/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: spring.io
Status: Confirmed
CVE: CVE-2026-40977 (🔒)
GCVE (CVE): GCVE-0-2026-40977
GCVE (VulDB): GCVE-100-359905
CERT Bund: WID-SEC-2026-1263 - VMware Tanzu Spring Boot: Mehrere Schwachstellen
CNNVD: CNNVD-202604-5558 - VMware Spring Boot 后置链接漏洞
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 04/28/2026 06:43Updated: 06/04/2026 15:43
Changes: 04/28/2026 06:43 (65), 04/30/2026 01:18 (6), 04/30/2026 13:04 (2), 06/04/2026 15:43 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.