Disclosed weakness · no CVE recorded

GPUStack watch streams could expose another tenant’s resource records

GPUStack · GPUStack

First documented disclosure · Review checkpoint

Summary

Live resource updates could expose another tenant’s credential records, worker pools or model-provider records to signed-in users.

Severity and exploitation evidence

Medium · 4.3/10 · CVSS 3.1. Severity source.

Exploitation not established: The original source establishes the weakness but does not report malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Live updates lacked tenant visibility filters applied to the ordinary list views.

Conditions required

An authenticated non-administrator can subscribe to an affected resource stream.

Potential impact

Cloud-credential records, worker-pool information and model-provider records could appear outside their tenant. Field-level redaction still matters.

Affected versions and configurations

>= 2.2.0, < 2.3.0

Fix and mitigation status

2.3.0 fixes this issue.

Practical next steps

Upgrade to 2.3.0 or a later release containing this fix. Restrict stream access and audit exposure of resource metadata.

Operating lesson

Apply the same tenant filters to subscriptions, initial snapshots and ordinary listings.

Evidence and limits

GPUStack shipped 2.3.0 on October 23. GitHub records an edit to the release notes on October 26, when GPUStack published the dated advisory. No CVE was listed in the advisory at review.

Sources