https://feed.craftedsignal.io/cpes/cpe2.3agpustackgpustack/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 10 Nov 2026 16:35:03 +0000https://feed.craftedsignal.io/favicon-32x32.pnghttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svghttps://feed.craftedsignal.io/briefs/2026-11-gpustack-auth-bypass/Tue, 10 Nov 2026 16:35:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-11-gpustack-auth-bypass/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.GPUStack versions 2.2.0 through 2.2.1 contain a missing authorization vulnerability in the cluster_apiserver_proxy 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.

Impact

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.

Recommendation

• Upgrade gpustack to version v2.2.2 or later immediately to patch CVE-2026-103002.
• Until the upgrade is deployed, restrict access to the GPUStack web interface and API to trusted administrative accounts only.
• Review Kubernetes RBAC roles and cluster role bindings associated with GPUStack worker ServiceAccounts to ensure they follow the principle of least privilege.

]]>highadvisoryvulnerabilityauthentication-bypasskubernetescloud-nativehttps://feed.craftedsignal.io/briefs/2026-11-gpustack-saml-bypass/Tue, 10 Nov 2026 16:34:10 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-11-gpustack-saml-bypass/GPUStack versions 0.7.1 through 2.2.1 are vulnerable to an authentication bypass in the /auth/saml/callback endpoint, allowing unauthenticated attackers to assume arbitrary identities, including administrator accounts, by submitting forged SAML assertions.GPUStack versions 0.7.1 through 2.2.1 contain a critical authentication bypass vulnerability due to improper handling of SAML assertions. The application fails to verify the SAML response signature, issuer, audience, destination, or time conditions using the expected OneLogin_Saml2_Auth.process_response() function. This vulnerability is active regardless of whether SAML SSO is configured, allowing an attacker to reach the /auth/saml/callback endpoint and authenticate as any user by posting a forged XML payload. Successful exploitation results in account takeover, including administrative access, and allows for infinite replay of captured assertions.

Impact

Successful exploitation grants an attacker full access to the target GPUStack deployment and any managed infrastructure. The vulnerability allows for identity spoofing of existing administrative users. Because the affected endpoint is enabled by default, all installations prior to 2.2.2 are at risk.

Recommendation

• Upgrade GPUStack to version 2.2.2 or later immediately to patch CVE-2026-102894.
• Until patching, block network access to the /auth/saml/callback URI at the reverse proxy or ingress level.
• Audit existing user sessions and logs for anomalous successful authentication events originating from unexpected or untrusted network sources.

]]>criticaladvisory