CVE-2026-59413
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Boot is an opinionated framework for building stand-alone, production-grade Spring applications with minimal configuration. Its actuator module adds production-ready features such as health checks and metrics, exposed as endpoints over HTTP.
An authorization bypass vulnerability (CVE-2026-59413) has been identified in the Spring Boot actuator, which allows attackers to set the value of an endpoint's @Selector parameter through a query parameter instead of the request path. Because the selected value no longer matches the path that was requested, security rules that match on the request path, such as rules protecting individual health groups or components, may be bypassed.
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: <=2.7.35, >=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 Medium-severity vulnerability is found in the org.springframework.boot:spring-boot-actuator package in multiple versions of Spring Boot.
Actuator endpoint operations can take @Selector parameters whose values come from the request path. The health endpoint, for example, exposes healthForPath(@Selector(match = Match.ALL_REMAINING) String... path), so a request to /actuator/health/db asks for the db component. When an operation is invoked over HTTP, the Spring MVC, WebFlux and Jersey endpoint adapters collect the path template variables, the remaining path segments and the request body into a single argument map keyed by parameter name. They then copy every query parameter into the same map, last. In the Spring MVC adapter, AbstractWebMvcEndpointHandlerMapping builds the map like this:
private Map<String, Object> getArguments(HttpServletRequest request, Map<String, String> body) {
Map<String, Object> arguments = new LinkedHashMap<>(getTemplateVariables(request));
String matchAllRemainingPathSegmentsVariable = this.operation.getRequestPredicate()
.getMatchAllRemainingPathSegmentsVariable();
if (matchAllRemainingPathSegmentsVariable != null) {
arguments.put(matchAllRemainingPathSegmentsVariable, getRemainingPathSegments(request));
}
if (body != null && HttpMethod.POST.name().equals(request.getMethod())) {
arguments.putAll(body);
}
request.getParameterMap()
.forEach((name, values) -> arguments.put(name,
(values.length != 1) ? Arrays.asList(values) : values[0]));
return arguments;
}
AbstractWebFluxEndpointHandlerMapping writes exchange.getRequest().getQueryParams() into the map last in the same way, and JerseyEndpointResourceFactory calls arguments.putAll(extractQueryParameters(data)) after arguments.putAll(extractPathParameters(data)). A query parameter whose name matches a selector parameter therefore replaces the value taken from the path. A request whose path matches a permitted pattern can carry a query parameter such as ?path=... that makes the operation act on a different selector value. Authorization rules written against the request path, for example with Spring Security's request matchers, check the path that was requested, while the endpoint returns data for the selector value supplied in the query string.
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.
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
- Daehyun Kang (finder)