Spring Boot's default security filter chain has no authorization rule with Actuator but without Health
Published 28 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.springframework.boot:spring-boot?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=4.0.0 <4.0.6
- Fixed in
- 4.0.6
mvn versions:use-dep-version -Dincludes=org.springframework.boot:spring-boot -DdepVersion=4.0.6 -DforceVersion=trueDetails
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.
Is GHSA-8v8j-3hxp-93wr in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework.boot:spring-boot, and gives you the command that fixes it.
More advisories for org.springframework.boot:spring-boot
- HighCVE-2026-40973Spring Boot accepts predictable temp directory without ownership verification · 28 Apr 2026
- HighCVE-2025-22235Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed · 28 Apr 2025
- HighCVE-2022-27772Temporary Directory Hijacking to Local Privilege Escalation Vulnerability in org.springframework.boot:spring-boot · 11 Jul 2022
- MediumCVE-2018-1196Moderate severity vulnerability that affects org.springframework.boot:spring-boot · 18 Oct 2018
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.