CVE-2026-59378
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Boot is an opinionated framework built on top of the Spring Framework that simplifies creating stand-alone, production-ready Java applications through auto-configuration, embedded servers and production features such as Actuator.
An authorization bypass vulnerability (CVE-2026-59378) has been identified in the default security configuration that Spring Boot applies to Actuator endpoints, which allows unauthenticated attackers to reach a Jersey application resource that requires authentication when that resource is mapped at the same path as the health endpoint.
Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
This issue affects multiple versions of Spring Boot.
Details
Module Info
- Product: Spring Boot
- Affected packages:
org.springframework.boot:spring-boot-actuator - Affected versions: >=3.0.0 <=3.4.18, >=3.5.0 <=3.5.17, >=4.0.0 <=4.0.9, >=4.1.0 <=4.1.2
- GitHub repository: https://github.com/spring-projects/spring-boot
- Published packages: https://central.sonatype.com/artifact/org.springframework.boot/spring-boot-actuator
- Package manager: Maven
- Fixed in:
- OSS Spring Boot 4.0.10, 4.1.3
- NES for Spring Boot
Vulnerability Info
This High-severity vulnerability is found in the org.springframework.boot:spring-boot-actuator package in multiple versions of Spring Boot.
When Spring Security is on the classpath and the application relies on the default security configuration, Spring Boot's ManagementWebSecurityAutoConfiguration registers a SecurityFilterChain that lets anyone reach the health endpoint and requires authentication for every other request. The health endpoint only serves GET requests, but the health matchers it uses are built from the endpoint's paths alone and carry no HTTP method restriction:
@Bean
@Order(SecurityProperties.BASIC_AUTH_ORDER)
SecurityFilterChain managementSecurityFilterChain(Environment environment, HttpSecurity http) throws Exception {
http.authorizeHttpRequests((requests) -> {
requests.requestMatchers(healthMatcher(), additionalHealthPathsMatcher()).permitAll();
requests.anyRequest().authenticated();
});
...
}
private RequestMatcher healthMatcher() {
return EndpointRequest.to(HealthEndpoint.class);
}
private RequestMatcher additionalHealthPathsMatcher() {
return EndpointRequest.toAdditionalPaths(WebServerNamespace.SERVER, HealthEndpoint.class);
}
The rule matches on the request path, not on which component handles the request. In a Jersey-based application (spring-boot-starter-jersey), the health endpoint can share its path with an application-provided JAX-RS resource, either through an additional health path (management.endpoint.health.probes.add-additional-paths=true, or a health group's additional-path) or through management.endpoints.web.base-path=/. Every request to that shared path, whatever its HTTP method, matches the permitAll() rule before the anyRequest().authenticated() rule is reached. A JAX-RS resource at that path that the application expects to be protected by the default authentication therefore accepts unauthenticated requests from remote attackers, including requests with methods such as POST, PUT or DELETE that the health endpoint itself never serves.
Mitigation
Only recent versions of Spring Boot receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.
Applications that cannot upgrade immediately can avoid the path collision: do not map a JAX-RS @Path resource under the path used by the health endpoint or its additional paths (for example /health/**, /livez, /readyz, or any Kubernetes probe path).
Users of the affected components should apply one of the following mitigations:
- Upgrade to a currently supported version of Spring Boot.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.
Credits
- h1ei1 (finder)