CVE-2026-59414
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 makes it easy to create stand-alone, production-grade Spring applications with minimal configuration, including auto-configured Actuator endpoints and Spring Security integration.
An authorization bypass vulnerability (CVE-2026-59414) has been identified in the Spring Security request matchers that Spring Boot creates through EndpointRequest and PathRequest, which allows attackers to reach Actuator endpoints or the H2 console without the intended security rules being applied when their path is configured with a trailing slash.
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-security,org.springframework.boot:spring-boot-actuator-autoconfigure,org.springframework.boot:spring-boot-autoconfigure - Affected versions:
org.springframework.boot:spring-boot-security: >=4.0.0 <=4.0.9, >=4.1.0 <=4.1.2org.springframework.boot:spring-boot-actuator-autoconfigure: <=2.7.35, >=3.0.0 <=3.4.18, >=3.5.0 <=3.5.17org.springframework.boot:spring-boot-autoconfigure: >=3.5.0 <=3.5.17- GitHub repository: https://github.com/spring-projects/spring-boot
- Published packages:
- https://central.sonatype.com/artifact/org.springframework.boot/spring-boot-security
- https://central.sonatype.com/artifact/org.springframework.boot/spring-boot-actuator-autoconfigure
- https://central.sonatype.com/artifact/org.springframework.boot/spring-boot-autoconfigure
- Package manager: Maven
- Fixed in:
- OSS Spring Boot 4.0.10, 4.1.3
- NES for Spring Boot
Vulnerability Info
This Critical-severity vulnerability is found in the org.springframework.boot:spring-boot-security, org.springframework.boot:spring-boot-actuator-autoconfigure and org.springframework.boot:spring-boot-autoconfigure packages in multiple versions of Spring Boot.
Applications commonly secure Actuator endpoints and the H2 console with the request matchers returned by EndpointRequest.to(...), EndpointRequest.toAnyEndpoint() and PathRequest.toH2Console(). These matchers build their patterns by appending /** to the configured path without removing a trailing slash first. In the servlet EndpointRequest, each endpoint path is joined to the suffix by plain string concatenation:
protected final List<RequestMatcher> getDelegateMatchers(RequestMatcherFactory requestMatcherFactory,
RequestMatcherProvider matcherProvider, Set<String> paths, HttpMethod httpMethod) {
return paths.stream()
.map((path) -> requestMatcherFactory.antPath(matcherProvider, httpMethod, path, "/**"))
.collect(Collectors.toCollection(ArrayList::new));
}
The reactive EndpointRequest does the same with new PathPatternParserServerWebExchangeMatcher(path + "/**", httpMethod), and the H2 console matcher behind PathRequest.toH2Console() is built the same way:
this.delegate = PathPatternRequestMatcher.withDefaults()
.matcher(h2ConsoleProperties.get().getPath() + "/**");
When an endpoint mapping or console path is configured with a trailing slash, for example management.endpoints.web.path-mapping.<id>=foo/ or spring.h2.console.path=/custom/, the resulting pattern contains a double slash (/custom//**). Such a pattern matches neither /custom nor /custom/x, while the endpoint or console itself is still served at those paths. The access rules attached to the matcher therefore never apply, and an unauthenticated attacker can reach the endpoint or the H2 console through the paths it actually serves, leaving it unintentionally unsecured.
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
- 李秉卓 (finder)
- LiZhiyao from BUPT (finder)