Skip to content
Fencer Vulns
critical 9.1

CVE-2026-40976 in the critical feed json

Spring Boot's default security filter chain has no authorization rule with Actuator but without Health

published 2026-04-27 6 mo ago modified 2026-09-10 1 mo ago also GHSA-8v8j-3hxp-93wr , EUVD-2026-25940

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

Summary

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.

Patch / fix

  • maven org.springframework.boot:spring-boot 4.0.6
  • Spring Spring Boot 4.0.6

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-40976 updated cvss 9.1

Spring Boot: Spring Boot: Security bypass due to ineffective default web security

  • Red Hat Data Grid 8 spring-boot
    affected: workaround, no fix available
  • Red Hat AMQ Broker 7 spring-boot, spring-boot-actuator-autoconfigure Red Hat AMQ Clients spring-boot Red Hat build of Apache Camel - HawtIO 4 spring-boot, spring-boot-actuator-autoconfigure Red Hat build of Apache Camel for Spring Boot 4 spring-boot, spring-boot-actuator-autoconfigure Red Hat build of OptaPlanner 8 spring-boot Red Hat Data Grid 8 spring-boot-actuator-autoconfigure
    +9 more products
    Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j Red Hat Fuse 7 spring-boot, spring-boot-actuator-autoconfigure Red Hat JBoss Enterprise Application Platform 7 spring-boot, spring-boot-actuator-autoconfigure Red Hat JBoss Enterprise Application Platform 8 spring-boot, spring-boot-actuator-autoconfigure Red Hat JBoss Enterprise Application Platform Expansion Pack spring-boot, spring-boot-actuator-autoconfigure Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Process Automation 7 spring-boot Red Hat Single Sign-On 7 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
yes
Technical impact
total
Assessed
6 mo ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.boot:spring-boot
>=4.0.0, <4.0.6
4.0.6

Affected products

  • Spring Spring Boot
  • Red Hat Red Hat AMQ Broker 7
  • Red Hat Red Hat AMQ Clients
  • Red Hat Red Hat build of Apache Camel for Spring Boot 4
  • Red Hat Red Hat build of Apache Camel - HawtIO 4
  • Red Hat Red Hat build of OptaPlanner 8
  • Red Hat Red Hat Data Grid 8
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat OpenShift Dev Spaces
  • Red Hat Red Hat Process Automation 7
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness
  • CWE-862 Missing Authorization
  • CWE-305 Authentication Bypass by Primary Weakness
Technology feeds

References

Sources

Fencer Vulns 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.