CVE-2026-40977 — Link Following in Spring Boot

CWE-59 — Link Following4 documents4 sources
Severity
4.7MEDIUMNVD
EPSS
0.0%
top 98.22%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
5
Spring BootApache Log4jDevspaces Openvsx-rhel9+2 more
Timeline
PublishedApr 28

Description

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.

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:HExploitability: 0.5 | Impact: 4.2

Affected Packages5 packages

▶CVEListV5spring/spring_boot4.0.0 — 4.0.6+4
▶Red Hatapache/log4j
▶Red Hatlog4j_2/log4j

🔴Vulnerability Details

1
VulDB
Vmware Spring Boot up to 4.0.5 PID File ApplicationPidFileWriter link following↗2026-04-28
▶

📋Vendor Advisories

1
Red Hat
Spring Boot: Spring Boot: Local file corruption via PID file manipulation↗2026-04-27
▶

💬Community

1
Bugzilla
CVE-2026-40977 Spring Boot: Spring Boot: Local file corruption via PID file manipulation↗2026-04-28
▶
CVE-2026-40977 — Link Following in Spring Boot | cvebase