# CVE-2026-58658: GPUStack Unauthenticated Information Disclosure via Worker Endpoints

> Unauthenticated attackers can access sensitive inference logs and modify worker configurations via unprotected endpoints in GPUStack.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-26wv-hf3j-hjjh

## What is CVE-2026-58658?

CVE-2026-58658 is a high-severity missing authorization vulnerability in gpustack, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-58658 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58658 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58658 is a high-severity missing authorization vulnerability in gpustack, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58658 exists.

Affected product: gpustack. 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-58658/ (Markdown: https://insights.sbomify.com/CVE-2026-58658/index.md)
```

## Sources

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

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