CVE-2026-59411

Incorrectly Configured Access Control
Affects
Spring Boot
in
Spring
No items found.
Versions
>=3.5.0 <=3.5.17, >=4.0.0 <=4.0.9, >=4.1.0 <=4.1.2

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Spring Boot is an open-source Java framework that makes it easy to create stand-alone, production-grade Spring applications through auto-configuration and opinionated defaults, with Actuator adding production-ready monitoring and management endpoints.

An incorrectly configured access control vulnerability (CVE-2026-59411) has been identified in the Spring Boot Cloud Foundry actuator auto-configuration, which allows unauthenticated attackers to access application endpoints that Spring Boot's default web security would otherwise protect. When a Servlet-based web application that uses Actuator is deployed to Cloud Foundry, the default web security is disabled. Reactive web applications and Servlet-based applications with their own security configuration are not affected.

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

Vulnerability Info

This Critical-severity vulnerability is found in the org.springframework.boot:spring-boot-actuator-autoconfigure and org.springframework.boot:spring-boot-cloudfoundry packages in multiple versions of Spring Boot.

When an application runs on Cloud Foundry, CloudFoundryActuatorAutoConfiguration exposes the Cloud Foundry actuator endpoints under /cloudfoundryapplication. Those endpoints are protected by their own security interceptor, so the auto-configuration tells Spring Security to let requests to them through by registering its own SecurityFilterChain bean:

@AutoConfiguration(after = { ServletManagementContextAutoConfiguration.class, HealthEndpointAutoConfiguration.class,
		InfoEndpointAutoConfiguration.class })
@ConditionalOnBooleanProperty(name = "management.cloudfoundry.enabled", matchIfMissing = true)
@ConditionalOnWebApplication(type = Type.SERVLET)
@ConditionalOnClass(DispatcherServlet.class)
@ConditionalOnBean(DispatcherServlet.class)
@ConditionalOnCloudPlatform(CloudPlatform.CLOUD_FOUNDRY)
public class CloudFoundryActuatorAutoConfiguration {

	// ...

	@ConditionalOnClass({ WebSecurityCustomizer.class, WebSecurity.class })
	@Configuration(proxyBeanMethods = false)
	public static class IgnoredCloudFoundryPathsWebSecurityConfiguration {

		private static final int FILTER_CHAIN_ORDER = -1;

		@Bean
		@Order(FILTER_CHAIN_ORDER)
		SecurityFilterChain cloudFoundrySecurityFilterChain(HttpSecurity http) throws Exception {
			RequestMatcher cloudFoundryRequest = getRequestMatcher();
			http.csrf((csrf) -> csrf.ignoringRequestMatchers(cloudFoundryRequest));
			CorsConfiguration corsConfiguration = getCorsConfiguration();
			http.cors((cors) -> cors.configurationSource((request) -> corsConfiguration));
			http.securityMatchers((matches) -> matches.requestMatchers(cloudFoundryRequest))
				.authorizeHttpRequests((authorize) -> authorize.anyRequest().permitAll());
			return http.build();
		}

	}

}

This filter chain only matches the Cloud Foundry paths. Everything else is meant to fall through to Spring Boot's default web security, which requires authentication for every request. That default configuration, and the default Actuator management security, are only applied under @ConditionalOnDefaultWebSecurity, which backs off as soon as any SecurityFilterChain bean is present:

class DefaultWebSecurityCondition extends AllNestedConditions {

	DefaultWebSecurityCondition() {
		super(ConfigurationPhase.REGISTER_BEAN);
	}

	@ConditionalOnClass({ SecurityFilterChain.class, HttpSecurity.class })
	static class Classes {

	}

	@ConditionalOnMissingBean({ SecurityFilterChain.class })
	static class Beans {

	}

}

CloudFoundryActuatorAutoConfiguration is not ordered after the servlet web security auto-configuration, so its cloudFoundrySecurityFilterChain bean is registered before the default security condition is evaluated. The condition then finds a SecurityFilterChain, the default security filter chain is never created, and the only filter chain left in the application is the one that matches /cloudfoundryapplication/**. Requests to any other path, including application endpoints and other Actuator endpoints, are not matched by any filter chain and are served without authentication. An application that relied on Spring Boot's default security to protect its endpoints is therefore exposed to unauthenticated remote access as soon as it is deployed to Cloud Foundry.

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 work around this issue by defining their own security configuration, so that protection no longer depends on Spring Boot's default web security.

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

Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Critical
ID
CVE-2026-59411
PROJECT Affected
Spring Boot
Versions Affected
>=3.5.0 <=3.5.17, >=4.0.0 <=4.0.9, >=4.1.0 <=4.1.2
NES Versions Affected
Published date
November 19, 2026
≈ Fix date
Category
Incorrectly Configured Access Control
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.