CVE-2026-59326

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-07-30. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
15(Track)
EG Risk 15/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 30, 2026

References (1)

Vendor Advisories for CVE-2026-59326(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-27 08:58 UTCEG score recompute
  3. 2026-08-27 08:58 UTCGHSA enrichment
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-24 06:13 UTCEG score recompute
  6. 2026-08-24 06:13 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 03:59 UTCEG score recompute
  10. 2026-08-21 03:59 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-18 02:05 UTCEG score recompute
  13. 2026-08-18 02:04 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-15 00:06 UTCGHSA enrichment
  19. 2026-08-11 22:11 UTCEG score recompute
  20. 2026-08-11 22:11 UTCGHSA enrichment
  21. 2026-08-08 20:16 UTCEG score recompute
  22. 2026-08-08 20:16 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 16 more
  1. 2026-08-05 18:21 UTCEG score recompute
  2. 2026-08-05 18:21 UTCGHSA enrichment
  3. 2026-08-04 15:10 UTCEPSS rescore
  4. 2026-08-03 10:36 UTCEPSS rescore
  5. 2026-08-02 16:27 UTCEG score recompute
  6. 2026-08-02 16:27 UTCGHSA enrichment
  7. 2026-08-01 04:16 UTCEPSS rescore
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 14:33 UTCEG score recompute
  10. 2026-07-30 14:33 UTCGHSA enrichment
  11. 2026-07-30 14:07 UTCEG score recompute
  12. 2026-07-30 14:07 UTCGHSA enrichment
  13. 2026-07-30 06:39 UTCEG score recompute
  14. 2026-07-30 06:39 UTCGHSA enrichment
  15. 2026-07-30 06:19 UTCEG score recompute
  16. 2026-07-30 06:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59326?
CVE-2026-59326 is a low vulnerability published on July 30, 2026. The Spring Boot language server logs the raw value of the httpsproxy/HTTPSPROXY/httpproxy/HTTPPROXY 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…
When was CVE-2026-59326 disclosed?
CVE-2026-59326 was first published in the National Vulnerability Database on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59326 actively exploited?
CVE-2026-59326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-59326?
CVE-2026-59326 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-59326?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59326, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59326

Explore →

Is Your Infrastructure Affected by CVE-2026-59326?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs