<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Gpustack (&lt; 2.2.2) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/gpustack--2.2.2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 10 Nov 2026 16:35:03 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/gpustack--2.2.2/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>GPUStack: Missing authorization in cluster API proxy (CVE-2026-103002)</title><link>https://feed.craftedsignal.io/briefs/2026-11-gpustack-auth-bypass/</link><pubDate>Tue, 10 Nov 2026 16:35:03 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-gpustack-auth-bypass/</guid><description>An authenticated user in GPUStack versions 2.2.0 to 2.2.1 can perform unauthorized actions on managed Kubernetes clusters by exploiting a missing authorization check in the Kubernetes API proxy handler.</description><content:encoded><![CDATA[<p>GPUStack versions 2.2.0 through 2.2.1 contain a missing authorization vulnerability in the <code>cluster_apiserver_proxy</code> handler. This flaw allows an authenticated non-administrative user to bypass resource-level authorization checks when forwarding requests to a Kubernetes cluster. The vulnerability stems from the proxy handler failing to validate user permissions before forwarding traffic through a worker node using its associated Kubernetes ServiceAccount.</p>
<h2 id="impact">Impact</h2>
<p>An attacker can leverage the ServiceAccount permissions of the worker node to interact with the Kubernetes cluster API. Depending on the privileges assigned to that ServiceAccount, observed and potential impacts include unauthorized reading of Kubernetes resources, modification of existing workloads, disruption of services through resource deletion, and potential remote code execution by creating attacker-controlled workloads.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade <code>gpustack</code> to version <code>v2.2.2</code> or later immediately to patch CVE-2026-103002.</li>
<li>Until the upgrade is deployed, restrict access to the GPUStack web interface and API to trusted administrative accounts only.</li>
<li>Review Kubernetes RBAC roles and cluster role bindings associated with GPUStack worker ServiceAccounts to ensure they follow the principle of least privilege.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>authentication-bypass</category><category>kubernetes</category><category>cloud-native</category></item></channel></rss>