Vulnerability in Vmware (CVE-2026-40977)
Summary
Vulnerability in Vmware (CVE-2026-40977). Risk of unauthorized operations or information disclosure. Exploitable via ApplicationPidFileWriter.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40977 has been found in Vmware.
Attackers can target a specific entry point like ApplicationPidFileWriter over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Vmware CVE-2026-40977" on the vendor's site.
CVE-2026-40977 (Vmware) — CWE-59 / CVSS v3 4.7
Attack vector: local / no user interaction
Attack surface: ApplicationPidFileWriter
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in Vmware. Attackers reach the vulnerable code path via ApplicationPidFileWriter.
Check the vendor advisory for the affected versions of Vmware. Attack surface: ApplicationPidFileWriter.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Vmware を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory nvd.nist.gov
- web spring.io