CVE-2026-40976
VMware Spring Boot broken access control
- Published27 Apr 2026
Description
In certain circumstances, Spring Boot's default web security is ineffective allowing unauthorized access to all endpoints. For an application to be vulnerable, it must: be a servlet-based web application; have no Spring Security configuration of its own and rely on the default web security filter chain; depend on spring-boot-actuator-autoconfigure; not depend on spring-boot-health. If any of the above does not apply, the application is not vulnerable. Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-40976 being actively exploited?
CVE-2026-40976 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.54%.
How severe is CVE-2026-40976?
CVE-2026-40976 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.54% probability of exploitation.
Which products are affected by CVE-2026-40976?
Affected products include VMware Spring Boot.
How do I fix CVE-2026-40976?
Upgrade affected software to a fixed version, for example VMware Spring Boot 4.0.6 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-40976 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.