Skip to main content
VulnerabilityPublished

CVE-2026-59327: Spring Tools for Eclipse · Cleartext Storage of Sensitive Information

Affects Spring Tools for EclipseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.4 Medium.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SpringSpring Tools for EclipseAffected
  • <=5.2.0
Fixed in–
Mavenorg.springframework.boot/spring-tools-for-eclipsepkg:maven/org.springframework.boot/spring-tools-for-eclipseOther threatsAffected
  • <=5.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should avoid sharing or committing .launch files containing the spring.devtools.remote.secret to version control or other shared locations. Restrict filesystem access to workspace metadata and project directories to trusted users only. Monitor vendor advisories for updates or official fixes addressing this issue.

Description

Spring Tools for Eclipse versions 5.2.0 and earlier store the Spring Boot DevTools remote secret in cleartext within launch configuration files. These files are saved as XML in the workspace metadata or project directories, potentially exposing the secret if accessed via filesystem, backups, or version control. The secret protects the remote restart/reload endpoint, which can execute arbitrary class bytes on the target application. Exposure of this secret could allow an attacker with read access to achieve remote code execution. The vulnerability has a medium severity with a CVSS score of 4.4.

References

Community reviews

Loading reviews…