Who is affected
GPUStack deployments are exposed to unauthenticated administrative compromise. The vulnerability permits attackers without credentials to assume full administrative control, manipulate users and models, create persistent API keys, extract secrets held by workers and cloud providers, and execute arbitrary code. The record does not specify which versions of GPUStack are affected.
How to check whether this touches you
- Inventory whether you run GPUStack anywhere in your estate, including development, staging and production environments.
- Establish whether your GPUStack instance is reachable over the network from untrusted sources (internet-facing, on a shared network segment, or accessible from containers or systems you do not fully control).
- Query your GPUStack deployment for its version number via its administrative interface or logs; version fingerprints are a signal of potential exposure but do not account for backported security patches applied by your vendor or distribution.
- Test whether the
/v2/inference-backends/from-yamlendpoint accepts POST requests without authentication headers or valid API keys.
What to do
- Treat this as urgent: the CISA federal remediation deadline is three days from the disclosure date. Review GPUStack's official security advisory and patch availability immediately.
- If a patch is available, plan and execute deployment within the deadline. Test patches in a non-production environment first.
- If no patch is available or you cannot meet the deadline, apply network-level mitigations: restrict access to GPUStack's administrative endpoints and the inference API to trusted internal sources only, using firewall rules, network segmentation, or reverse-proxy authentication.
- Enable and retain all authentication and API request logs, including failed authentication attempts and POST requests to
/v2/inference-backends/from-yaml, for the retrospective investigation phase. - If GPUStack is internet-facing and no patch or mitigation is available, evaluate whether you can discontinue use of the product, as CISA guidance permits.
- Escalate to your security team if the instance has been internet-reachable or if you cannot establish a patch timeline within 72 hours.
If you find you were exposed
Exploitation of this flaw predates public disclosure by an unknown margin, so retrospective investigation must assume a longer window than the three-day deadline. Review authentication logs and API request logs from as far back as your retention policy allows, hunting for requests to /v2/inference-backends/from-yaml lacking valid credentials, and for creation of new administrator API keys outside your normal change process. Extract and rotate any worker and cloud-provider secrets stored in GPUStack, as these are likely to have been accessed if the instance was exposed to the internet.