cve.bz

CVE-2026-40976 vmware spring boot: Missing Authorization

9.1 criticalEPSS 0.5%Fix available

Critical (9.1) in vmware spring boot. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.boot:spring-boot 4.0.6.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-862 Missing Authorization
CWE-305 Authentication Bypass by Primary Weakness
OWASP Top 10
A01:2025 Broken Access Control, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40976 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40976?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40976?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40976 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Bootfrom 4.0.0 before 4.0.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8v8j-3hxp-93wrMavenorg.springframework.boot:spring-boot>=4.0.0 <4.0.64.0.6

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is an Important flaw in Spring Boot that allows security bypass under specific application configurations. When a servlet-based web application lacks custom Spring Security configuration, relies on the default web security filter chain, depends on `spring-boot-actuator-autoconfigure`, and does not include `spring-boot-health`, an attacker can gain unauthorized access to all application endpoints. Red Hat JBoss Data Grid (jdg-8.6) is affected by this vulnerability.

Red Hat's mitigation

To mitigate this flaw, ensure that Spring Boot applications either implement their own Spring Security configuration, thereby not relying on the default web security filter chain, or include a dependency on `spring-boot-health`. Applications that do not meet all the specific conditions outlined for vulnerability are not affected. If `spring-boot-actuator-autoconfigure` is not strictly required, consider removing it.

ProductPackageStateAdvisory
Red Hat AMQ Broker 7spring-bootNot affected
Red Hat AMQ Broker 7spring-boot-actuator-autoconfigureNot affected
Red Hat AMQ Clientsspring-bootNot affected
Red Hat build of Apache Camel for Spring Boot 4spring-bootNot affected
Red Hat build of Apache Camel for Spring Boot 4spring-boot-actuator-autoconfigureNot affected
Red Hat build of Apache Camel - HawtIO 4spring-bootNot affected
Red Hat build of Apache Camel - HawtIO 4spring-boot-actuator-autoconfigureNot affected
Red Hat build of OptaPlanner 8spring-bootNot affected
Red Hat Data Grid 8spring-bootAffected
Red Hat Data Grid 8spring-boot-actuator-autoconfigureNot affected
Red Hat Enterprise Linux 8log4j:2/log4jNot affected
Red Hat Enterprise Linux 9log4jNot affected
Red Hat Fuse 7spring-bootNot affected
Red Hat Fuse 7spring-boot-actuator-autoconfigureNot affected
Red Hat JBoss Enterprise Application Platform 7spring-bootNot affected
Red Hat JBoss Enterprise Application Platform 7spring-boot-actuator-autoconfigureNot affected
Red Hat JBoss Enterprise Application Platform 8spring-bootNot affected
Red Hat JBoss Enterprise Application Platform 8spring-boot-actuator-autoconfigureNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packspring-bootNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packspring-boot-actuator-autoconfigureNot affected
4 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-40976.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON