GPUStack through 2.2.1, fixed in commit 4e20551, contains an unauthenticated information disclosure vulnerability that allows unauthenticated attackers to access sensitive inference logs and modify worker configuration by exploiting unprotected /serveLogs and /debug endpoints on the worker port. Attackers can enumerate model instance IDs to stream serving logs containing prompts and completions, change log levels, and read memory profiling data without any authentication.
CVE-2026-58658
This high-severity CVE scores 8.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026GPUStack worker exposes /serveLogs and /debug without authentication · Issue #5836 · gpustack/gpustack · GitHub
https://github.com/gpustack/gpustack/issues/5836GPUStack Unauthenticated Information Disclosure via Worker Endpoints | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gpustack-unauthenticated-information-disclosure-via-worker-endpointscommit 4e20551b5aaf (gpustack/gpustack)
Fix landed in gpustack/gpustack commit 4e20551b5aaf — awaiting tagged release
https://github.com/gpustack/gpustack/commit/4e20551b5aaf76f93a8769d32b7fef999e22a4d3Vendor Advisories for CVE-2026-58658(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 2× in last 7d / 2× 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.
- 2026-07-15 17:29 UTCEG score recompute
- 2026-07-15 17:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
- CVE-2006-0061EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-58658?
When was CVE-2026-58658 disclosed?
What is the CVSS score of CVE-2026-58658?
How do I remediate CVE-2026-58658?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58658
Is Your Infrastructure Affected by CVE-2026-58658?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.