# CVE-2026-59326: HTTP Proxy Credentials Logged in Plaintext by the Spring Boot Language Server

> The Spring Boot language server logs proxy credentials in plaintext, potentially exposing sensitive authentication data to local users or bug reports.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-9j65-vr9q-w452

## What is CVE-2026-59326?

CVE-2026-59326 is a low-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Spring Boot language server logs the raw value of the https_proxy/HTTPS_PROXY/http_proxy/HTTP_PROXY environment variable at INFO level whenever it creates an outbound HTTP client and no explicit http.proxy workspace setting is configured. Corporate proxy URLs frequently embed Basic-auth credentials in the form http://user:pass@proxy:8080, and the language server writes this value to its log file without any redaction. Since language server log files are often attached to bug reports or are readable by other local users/processes, this can result in disclosure of proxy credentials.
Affected Spring Products and Versions:
Spring Tools for Eclipse: 5.2.0 and earlier
Spring Tools for VSCode / Cursor / Theia: 2.2.0 and earlier

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Broadcom Spring Tools.

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

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

## Is CVE-2026-59326 being exploited?

There is no known exploitation of CVE-2026-59326 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-59327](https://insights.sbomify.com/CVE-2026-59327/): Cleartext Storage of Spring Boot DevTools Remote Secret in Eclipse Launch Configurations (medium 4.4)
- [CVE-2026-59328](https://insights.sbomify.com/CVE-2026-59328/): Cross-Site Scripting in Eclipse Spring Boot Starter Wizard Dependency Tooltips (medium 4.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59326 is a low-severity vulnerability in Spring Tools for Eclipse, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59326 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-59326/ (Markdown: https://insights.sbomify.com/CVE-2026-59326/index.md)
```

## Sources

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

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