Skip to content
Fencer Intel
medium 4.7

CVE-2026-40977 json

Spring Boot's PID file write follows symlinks at predictable default path

published 6mo ago modified 3mo ago also GHSA-5368-6h4h-gr29 , EUVD-2026-25941

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.boot:spring-boot-cassandra 3.5.14, 4.0.6
  • Spring Spring Boot 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6

Is CVE-2026-40977 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-40977 updated cvss 5.3

Spring Boot: Spring Boot: Local file corruption via PID file manipulation

  • Red Hat AMQ Broker 7 spring-boot Red Hat AMQ Clients spring-boot Red Hat build of Apache Camel - HawtIO 4 spring-boot Red Hat build of OptaPlanner 8 spring-boot Red Hat Data Grid 8 spring-boot Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7 spring-boot Red Hat JBoss Enterprise Application Platform 7 spring-boot Red Hat JBoss Enterprise Application Platform 8 spring-boot Red Hat JBoss Enterprise Application Platform Expansion Pack spring-boot Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Process Automation 7 spring-boot
    +1 more products
    Red Hat Single Sign-On 7 spring-boot
    affected: no fix available “Fix deferred”
  • Red Hat build of Apache Camel for Spring Boot 4 spring-boot
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6mo ago

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
NVD 3.1 6.7 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.boot:spring-boot-cassandra
>=4.0.0, <4.0.6
>=3.5.0, <3.5.14
>=3.4.0, <=3.4.15
>=3.3.0, <=3.3.18
<=2.7.32
4.0.6
3.5.14

Affected products

  • Spring Spring Boot

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.