Spring Boot · CVE-2026-59414
Spring Boot slash
Patch now if…Only bites if a configured path ends in /. No exploit.
Spring rates this Spring Boot bug Critical. Spring Boot builds security rules for Actuator endpoints and the H2 console from paths in your configuration; if such a path ends in a slash, the rule comes out wrong and doesn't match the real endpoint, which can then be left unsecured. The fix only strips that slash, so paths without one behave the same before and after. Free fixes exist only for Spring Boot 4.0 and 4.1.
Part of the Spring Nov release roundup: see all 90 advisories →
How scary is it?
Are you affected? only if all are true
1Spring Boot 4.1.2 or oldercommand
Affected: 4.1.0 to 4.1.2, 4.0.0 to 4.0.9, 3.5.0 to 3.5.17, 3.0.0 to 3.4.18, and 2.7.35 and older.1
mvn dependency:list | grep spring-boot2Rules use EndpointRequest or the H2 console matcher
Your Spring Security config builds rules with EndpointRequest (Actuator, servlet or reactive) or PathRequest.toH2Console(). The fix didn't change the static-resource matchers.1,2
3A configured path ends in /command
For example management.endpoints.web.path-mapping.health=status/ or spring.h2.console.path=/custom/, which produce a rule for /actuator/status//** that never matches /actuator/status. The fix also covers health group additional paths and / as the Actuator base path. Look for those properties and check whether a value ends in a slash.2
grep -rnE "path-mapping|console.path|base-path|additional-path" src/main/resources/4A later rule is looser
Spring Security checks rules in order and uses the first that matches. When the broken rule doesn't match, the request falls through to your next rule, so the endpoint is only left open if that rule is looser, for example anyRequest().permitAll().4,1
What to do
1Upgrade to 4.1.3 or 4.0.10
Spring Boot 4.2.0, released the same day, also contains the fix.1,3
Latest safe versions checked 20 Nov
2Or drop the trailing slash
The fix strips trailing slashes from configured paths. Removing them from your configuration yourself should have the same effect; Spring's advisory doesn't list a workaround.2,1
3On Boot 3.x or older: no free fix
Spring's fixes for 3.5, 3.4 and 2.7 (3.5.18, 3.4.19, 2.7.36) are only for Enterprise support customers, so the configuration check above is your option.1
This page shows you how to check. It can't tell you you're safe.
Sources (5) and changelog
- Spring: CVE-2026-59414 advisory 19 Nov
- Spring Boot: fix commit and tests, "Normalize paths when creating request matchers" (4.1.x)
- Spring Boot: same fix on main, included in v4.2.0
- Spring Security docs: request rules are checked in order
- CISA KEV catalog: not listed
- Published.