CVE-2026-59327
MediumCVSS 4.4Exploitation Probability (EPSS)
Low risk0th percentile - higher than 0% of all known CVEs
Summary
Spring Tools for Eclipse stores the Spring Boot DevTools remote secret as plain text in the launch configuration. The .launch file is saved as cleartext XML, potentially leaking the secret to the filesystem or version control.
Risk Assessment
Anyone with access to the .launch file can read the secret and remotely execute arbitrary code on the target Spring Boot application via the DevTools endpoint.
Recommendation
Update Spring Tools for Eclipse to a version later than 5.2.0. Do not share .launch files in repositories or store them in insecure locations.
Other vulnerabilities in Spring Tools for Eclipse
See all- CVE-2026-59328Medium
Spring Tools for Eclipse renders Spring Boot starter wizard dependency tooltips in a native embedded browser with JavaScript enabled. Untrusted or compromised Initializr endpoints can lead to arbitrary script execution when hovering a dependency checkbox.
- CVE-2026-59326Low
The Spring Boot language server logs the raw value of proxy environment variables (https_proxy, etc.) at INFO level when no http.proxy setting is configured. Proxy URLs often contain Basic-auth credentials, which are written without redaction.
- CVE-2026-47882High
When enabling Spring Boot DevTools support for a remote application target from the Spring Tools Boot Dashboard, Spring Tools generates a shared secret that authenticates DevTools remote-restart uploads. This secret was generated using a non-cryptographic pseudo-random number generator rather than a cryptographically secure source of randomness. Affects Spring Tools for Eclipse 5.2.0 and earlier.
- CVE-2026-47873High
The Boot Dashboard Docker integration in Spring Tools publishes container control ports on all of the host's network interfaces (0.0.0.0) rather than restricting them to loopback. Affects Spring Tools for Eclipse 5.2.0 and earlier.
Original NVD description (English source)
Spring Tools for Eclipse stores the Spring Boot DevTools remote secret (spring.devtools.remote.secret) as a plain string attribute on the "Spring Boot DevTools Client" launch configuration. Eclipse persists launch configuration attributes as cleartext XML, either to workspace metadata or, if the user marks the configuration as a shared file, directly into the project tree where it can be committed to version control. This secret is the sole credential protecting the DevTools remote restart/reload endpoint, which accepts and executes arbitrary class bytes on the target application. Anyone able to read the .launch file (via filesystem access, a workspace backup, or a shared VCS repository) can extract the secret and use it to achieve remote code execution against the associated Spring Boot application. Affected Spring Products and Versions: Spring Tools for Eclipse: 5.2.0 and earlier