CVE-2026-58658
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGPUStack 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGPUStack through version 2.2.1 contains unprotected /serveLogs and /debug endpoints on the worker port that lack authentication, allowing unauthenticated attackers to access sensitive inference logs containing prompts and completions, enumerate model instance IDs, change log levels, and read memory profiling data, while also enabling modification of worker configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GPUStack installation and versionRun 'gpustack --version' or check the installed package version to determine if it is 2.2.1 or earlierAffected if Version is 2.2.1 or any earlier version
-
Identify the worker port configurationCheck GPUStack configuration files or running process for the worker port number (typically in the 50050-50060 range or defined in config)Affected if Worker port is exposed to untrusted network interfaces
-
Verify /serveLogs endpoint accessibilitySend an HTTP GET request to http://[worker-host]:[worker-port]/serveLogs without providing any authentication credentialsAffected if The endpoint returns log data without requiring authentication
-
Verify /debug endpoint accessibilitySend an HTTP GET request to http://[worker-host]:[worker-port]/debug without providing any authentication credentialsAffected if The endpoint returns debug information, memory profiling data, or configuration details without requiring authentication
-
Check for sensitive data exposureExamine the response from /serveLogs for inference prompts, completions, or model instance IDs that should be protectedAffected if Sensitive inference data (prompts, completions, model IDs) is visible without authentication
You are affected if GPUStack version 2.2.1 or earlier is running with worker port accessible to untrusted users and the /serveLogs or /debug endpoints respond without authentication challenges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication and authorization controls on the /serveLogs and /debug endpoints, restrict access to trusted users only, and validate all input parameters to prevent enumeration attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58658 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data