Vulnary
← back to the feed
Critical· 9.1official fix available

CVE-2026-40976

Spring Boot versions 4.0.0 through 4.0.5 have a flaw that lets anyone access all web endpoints when the application uses the default security settings. The issue only appears in servlet‑based apps that don’t add their own Spring Security configuration and that include the actuator autoconfigure module. An attacker can read or modify data without authentication.

publishedApr 28, 2026
last modifiedJul 24, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
39th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 25, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Spring Boot 4.0.0–4.0.5 servlet‑based web applications that rely on the default security filter chain, have no custom Spring Security configuration, and include spring‑boot‑actuator‑autoconfigure but not spring‑boot‑health. Developers deploying these versions without additional security measures are at risk.

02

Real-world impact

An attacker who can reach the application can read sensitive data, change configuration, or perform actions that normally require authentication, effectively taking full control of the web service.

03

Why this severity

The CVSS score of 9.1 reflects that no authentication or user interaction is needed, and the vulnerability can compromise both confidentiality and integrity of the application data.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Spring Boot to version 4.0.6 or later.
  2. 02Restart the application to apply the new version.

NVD-referenced vendor advisory

05

Timeline

  1. Apr 28, 2026 · Apr 28, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 24, 2026 · 11d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 26, 2026 · 10d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →