CVE-2026-59409
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, metrics and management endpoints, including a heapdump endpoint that returns a dump of the JVM heap.
An information exposure vulnerability (CVE-2026-59409) has been identified in Spring Boot Actuator, which allows other local users on the host to read the heap dump that the heapdump endpoint writes to a temporary file. A heap dump contains the application's in-memory data, which can include credentials, session tokens, keys and other sensitive values.
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. When the application runs on a HotSpot JVM, a request to the Actuator heapdump endpoint makes HeapDumpWebEndpoint pick the dump location with java.io.File.createTempFile in the JVM's shared temporary directory (java.io.tmpdir, usually /tmp) and then ask HotSpotDiagnosticMXBean.dumpHeap to write the heap to that path. In the 3.x and 4.x lines this happens in its HotSpotDiagnosticMXBeanHeapDumper:
@Override
public File dumpHeap(Boolean live) throws IOException {
File file = createTempFile();
ReflectionUtils.invokeMethod(this.dumpHeapMethod, this.diagnosticMXBean, file.getAbsolutePath(),
(live != null) ? live : true);
return file;
}
private File createTempFile() throws IOException {
String date = DateTimeFormatter.ofPattern("yyyy-MM-dd-HH-mm").format(LocalDateTime.now());
File file = File.createTempFile("heap-" + date, ".hprof");
file.delete();
return file;
}File.createTempFile does not restrict the file to its owner: on POSIX systems the file's permissions follow the process umask, which typically leaves it readable by other users. The resulting .hprof file in the shared temporary directory can therefore be read by any other local user while it exists, exposing the full contents of the application's heap. Exploitation requires a low-privileged local account on the same host and an invocation of the heapdump endpoint, which is not accessible by default and must be exposed by the application. Older lines that predate HeapDumpWebEndpoint, such as the 1.5.x line, create the heap dump file the same way in HeapdumpMvcEndpoint.
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.