CVE-2026-59372
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Boot is a framework built on the Spring Framework for creating stand-alone, production-grade Spring applications with minimal configuration. Its Actuator module adds production-ready features such as health, environment and configuration properties endpoints, and sanitizes sensitive values before those endpoints return them.
An information exposure vulnerability (CVE-2026-59372) has been identified in Spring Boot Actuator's value sanitization, which allows attackers with access to Actuator endpoints to read values that should have been masked when the application runs with a Turkish or Azerbaijani default locale.
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.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 Low-severity vulnerability is found in the org.springframework.boot:spring-boot-actuator package in multiple versions of Spring Boot. Actuator endpoints such as /actuator/env and /actuator/configprops pass every value through Sanitizer, which applies the application's SanitizingFunction beans when unsanitized values are allowed to be shown. The convenience filters ifKeyEquals, ifKeyEndsWith and ifKeyContains, and the presets built on them (ifLikelySensitive, ifLikelyCredential, ifLikelyUri and ifVcapServices), match keys case-insensitively by lowercasing both the key and the expected value. Both conversions use the JVM's default locale:
// SanitizableData
public String getLowerCaseKey() {
String result = this.lowerCaseKey;
if (result == null && this.key != null) {
result = this.key.toLowerCase(Locale.getDefault());
this.lowerCaseKey = result;
}
return result;
}
// SanitizingFunction
private Predicate<SanitizableData> onKeyIgnoringCase(BiPredicate<String, String> predicate, String value) {
Assert.notNull(predicate, "'predicate' must not be null");
Assert.notNull(value, "'value' must not be null");
String lowerCaseValue = value.toLowerCase(Locale.getDefault());
return (data) -> nullSafeTest(data.getLowerCaseKey(),
(lowerCaseKey) -> predicate.test(lowerCaseKey, lowerCaseValue));
}In the Turkish and Azerbaijani locales, String.toLowerCase maps the uppercase Latin I to the dotless ı rather than to i. A key that contains an uppercase I, which is common for environment variables, therefore no longer matches a rule written with a lowercase i. For example, DATABASE_URI becomes database_urı and fails ifKeyEndsWith("uri"), and APP_CREDENTIALS becomes app_credentıals and fails ifKeyContains("credentials"). The sanitizing function is skipped and the endpoint returns the original value, so credentials, connection URIs and other secrets that the application configured Actuator to mask are disclosed to anyone who can read the endpoint.
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
- Mingyu Park from Woowa Brothers (finder)
- SharlongWen (finder)