# CVE-2026-59327: Cleartext Storage of Spring Boot DevTools Remote Secret in Eclipse Launch Configurations

> Attackers with filesystem or VCS access can extract cleartext DevTools secrets from Eclipse launch configs to achieve remote code execution on Spring Boot apps.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-xg26-wm7c-xr7g

## What is CVE-2026-59327?

CVE-2026-59327 is a medium-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-59327?

It affects 1 product.


Products: Broadcom Spring Tools.

## How do I fix CVE-2026-59327?

No fix has been published for CVE-2026-59327 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59327 being exploited?

There is no known exploitation of CVE-2026-59327 in the wild and no public exploit code.

## Other vulnerabilities in Spring Tools for Eclipse

- [CVE-2026-47882](https://insights.sbomify.com/CVE-2026-47882/): Spring Boot DevTools remote secret generated with a non-cryptographic PRNG (high 8.3)
- [CVE-2026-47858](https://insights.sbomify.com/CVE-2026-47858/): live information startup mode is vulnerable for remote code execution (high 8.0)
- [CVE-2026-47873](https://insights.sbomify.com/CVE-2026-47873/): Spring Tools Docker integration publishes unauthenticated debug (JDWP) and JMX ports on all network interfaces (high 8.0)
- [CVE-2026-59328](https://insights.sbomify.com/CVE-2026-59328/): Cross-Site Scripting in Eclipse Spring Boot Starter Wizard Dependency Tooltips (medium 4.2)
- [CVE-2026-59326](https://insights.sbomify.com/CVE-2026-59326/): HTTP Proxy Credentials Logged in Plaintext by the Spring Boot Language Server (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59327 and fix it if it is affected.

What it is: CVE-2026-59327 is a medium-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-59327 in the wild and no public exploit code.

Affected product: Spring Tools for Eclipse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59327/ (Markdown: https://insights.sbomify.com/CVE-2026-59327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59327
- OSV: https://osv.dev/vulnerability/CVE-2026-59327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59327/
Summaries are generated and may contain mistakes; the official description above is the record.