Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-40977: When an application is configured to use `ApplicationPidFileWriter`, a local attacker with write access to the

17
Routine
MEDIUM 4.7UPGRADE

CVE-2026-40977 is a medium-severity flaw (CVSS 4.7) affecting spring boot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 suppor

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.7 (Medium)
Attack vectorLocal
Attack complexityHigh
Privileges neededHigh
User interactionNone
EPSS exploit chance0.1% (top 99%)
CISA exploited listNo
WeaknessCWE-59
Published2026-04-28
Last modified2026-07-24
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring boot UPGRADE
Affected: < 2.7.33 · >= 3.3.0 and < 3.3.19 · >= 3.4.0 and < 3.4.16 · >= 3.5.0 and < 3.5.14 · >= 4.0.0 and < 4.0.6
Fixed in: 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6
Safe to downgrade to: a release before 3.3.0
1. Check installed version
apt-cache policy spring-boot || rpm -q spring-boot || spring-boot --version
2. UPGRADE to 2.7.33 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-boot
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-boot
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.3.0 (Debian / Ubuntu)
apt-cache madison spring-boot sudo apt install spring-boot=<VERSION_BEFORE_3.3.0> sudo apt-mark hold spring-boot
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-boot sudo dnf downgrade spring-boot-<VERSION_BEFORE_3.3.0> sudo dnf versionlock add spring-boot
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40977?

spring boot: upgrade to 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6. Exact commands for each OS are on this page.

Is CVE-2026-40977 being exploited?

CVE-2026-40977 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40977 affect?

CVE-2026-40977 affects spring boot. Severity is medium (CVSS 4.7). 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 (fi

How urgent is CVE-2026-40977?

Priority 17/100. No elevated risk signals yet.

Software pages

Spring Framework vulnerabilities · VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.