CVE-2026-40977: Medium severity VMware Spring Boot vulnerability

Published Apr 27, 2026
·
Updated

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.

Affected Software

7 affected components
VMware Spring Boot>=4.0.0<=4.0.5, >=3.5.0<=3.5.13, >=3.4.0<=3.4.15, >=3.3.0<=3.3.18, >=2.7.0<=2.7.32
VMware Spring Boot<2.7.33
VMware Spring Boot>=3.3.0<3.3.19
VMware Spring Boot>=3.4.0<3.4.16
VMware Spring Boot>=3.5.0<3.5.14
VMware Spring Boot>=4.0.0<4.0.6
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 4.0.6
  2. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.5.14
  3. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.4.16
  4. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.3.19
  5. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 2.7.33

Event History

Apr 27, 2026
CVE Published
via MITRE·11:36 PM
Data Sourced
via MITRE·11:36 PM
DescriptionSeverityWeakness
Apr 28, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40977?

CVE-2026-40977 is classified as a high severity vulnerability due to the potential for local attackers to corrupt files on the host system.

2

How do I fix CVE-2026-40977?

To fix CVE-2026-40977, upgrade your Spring Boot application to version 4.0.6, 3.5.14, or 3.4.16 or later.

3

Who is affected by CVE-2026-40977?

CVE-2026-40977 affects users of VMware Spring Boot versions 4.0.0 through 4.0.5, 3.5.0 through 3.5.13, and 3.4.0 through 3.4.15.

4

What can an attacker do exploiting CVE-2026-40977?

An attacker exploiting CVE-2026-40977 can corrupt a file on the host each time the application using ApplicationPidFileWriter is started.

5

How can I determine if I'm vulnerable to CVE-2026-40977?

You can determine your vulnerability to CVE-2026-40977 by checking if your Spring Boot application is running on the affected versions listed.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203