English edition · cyberattaques.org in FrenchFrançais
VulnerabilityExploited

Exploited GPUStack authentication flaw grants unauthenticated admin access and code execution

On 9 November 2026, CISA added CVE-2026-102895 to its Known Exploited Vulnerabilities catalogue. The flaw lets attackers gain unauthenticated administrative access to GPUStack and execute code, which concerns any organisation running the GPU cluster manager, and US federal agencies must address it by 12 November 2026.

What to do now Illustration photo (network cables)
CVSS severity9.8Critical
EPSS probability6 %
ExploitationConfirmed (CISA KEV)
PatchNone
Product
GPUStack
Affected versions
—
CVE
CVE-2026-102895

CISA added CVE-2026-102895, a vulnerability in GPUStack, to its Known Exploited Vulnerabilities catalogue on 9 November 2026. GPUStack is an open-source tool for managing GPU clusters and serving AI models. CISA notes that it is a component that other products may also incorporate.

The flaw lies in GPUStack's authentication handling. The weaknesses cited are improper authentication, authentication bypass by spoofing and origin validation errors. An unauthenticated attacker can use them to gain administrative control.

With that control, an attacker can change users and models, create persistent administrator API keys, and read secrets belonging to workers and configured cloud providers. They can also run code by sending a POST request to the /v2/inference-backends/from-yaml endpoint. Because attacker-created API keys can outlive a patch, updating alone will not clean up an instance that was already breached.

The source does not list affected or fixed versions. It points instead to the project's GitHub security advisory, GHSA-gj9m-f8ph-pmhr. CISA has not determined whether the flaw has been used in ransomware campaigns.

Under Binding Operational Directive 26-04, US federal agencies have until 12 November 2026 to apply the vendor's mitigations. CISA has also flagged the entry for forensic triage. Agencies that cannot mitigate must stop using the product.

Action plan

What to do now

  1. Apply the fix or mitigations described in GPUStack's GitHub advisory GHSA-gj9m-f8ph-pmhr immediately.
  2. If no mitigation can be applied, remove internet access to the GPUStack interface and API or shut the service down.
  3. Review user accounts, deployed models and inference backends, and revoke any administrator API keys you cannot account for.
  4. Rotate worker secrets and cloud-provider credentials stored in GPUStack, since they may have been exposed.
  5. Check logs for POST requests to /v2/inference-backends/from-yaml and other unexpected administrative actions that could indicate compromise.

Sources