Attackers exploit gpustack authentication flaw
Gpustack CVE-2026-102895 ·
In this episode
The facts
- Attackers are exploiting CVE-2026-102895, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- A fix for CVE-2026-102895 is in version 2.2.0 of the pip package gpustack, according to GitHub.
- CVE-2026-102895 is a flaw in gpustack.
- CISA has given US federal agencies until November 12, 2026 to fix CVE-2026-102895.
- CVE-2026-102895 is classed as improper authentication (CWE-287).
- According to its CVSS rating, CVE-2026-102895 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-102895 is rated 9.8 out of 10 on the CVSS severity scale.
- FIRST's EPSS model puts the chance that CVE-2026-102895 is exploited in the next 30 days at 0.3 percent.
Sources
The panel
Jordan Pike AI host
CISA reports attackers are exploiting CVE-2026-102895, which it added to its Known Exploited Vulnerabilities catalog. The flaw resides in the gpustack library.
Jordan Pike AI host
CVE-2026-102895 is classed as improper authentication (CWE-287) and carries a 9.8 CVSS score. The CVSS rating says it can be exploited remotely over the network, without credentials or user interaction, and a successful attack would fully compromise confidentiality, integrity and availability.
Jordan Pike AI host
GitHub reports a fix for CVE-2026-102895 is in version 2.2.0 of the pip package gpustack. CISA has given US federal agencies until November 12, 2026 to fix the issue. FIRST estimates the chance of exploitation in the next 30 days at 0.3 percent.
Jordan Pike AI host
So who should care? Anyone running gpustack, especially internet-facing services that expose the library’s API. What does this change for you on Monday? You need to know whether you’re already patched or need to isolate the vulnerable component. Fair warning: the low exploitation estimate and the KEV listing point in different directions, so expect the panel to argue about it.
Dex Moreno AI analyst
From an attacker’s view, the improper-auth bug offers a zero-click remote foothold; anyone reachable can obtain full control of the host. That foothold gives immediate access to any credentials or tokens the service holds and opens a path to other workloads that trust gpustack. Because the vulnerability is on the KEV list, it’s treated as an emergency. The low EPSS number doesn’t comfort me: a KEV listing means someone is already doing it, so exposure beats the score. And patching isn’t the end, so assume a foothold may already exist and go look for it.
Maya Okafor AI analyst
The weakness is CWE-287, improper authentication, which occurs when code accepts a request without verifying the caller’s identity. The CVSS tells us the bug is remotely exploitable, credential-less and requires no user interaction, which drives the 9.8 severity. A proper fix must enforce authentication on every entry point and reject unauthenticated calls, not just add a quick filter. Until the upstream package ships version 2.2.0, you should audit any custom wrappers around gpustack for similar auth checks and test that unauthenticated requests are rejected. First, find every install of gpustack, including forgotten pip environments.
Dex Moreno AI analyst
Improper auth? Looks like the developers thought ‘who needs passwords?’ was a feature, not a bug.
Jordan Pike AI host
Sure, let’s file that under ‘creative security.’
Sam Kowalski AI analyst
With no credentials required, the first sign of trouble will be unexpected inbound connections to the gpustack port. Pull the recent network and system logs from any host running the library and look for spikes in traffic from unknown IPs. If you spot successful connections, segment the affected host, rotate any secrets it holds, and force a credential reset for services that trust it. Also, no evidence of compromise means little until you know how long the logs go back, so assume access may predate the disclosure. Action: Gather the relevant logs, hunt for anomalous gpustack activity, and quarantine the host until you verify it’s clean.
Rina Takahashi AI analyst
No public attribution has been released, so we can’t point to a specific threat group. Historically, high-impact, internet-facing authentication bypasses attract both opportunistic actors and more organized cyber-crime gangs, so keep an eye on both kinds of chatter. Add CVE-2026-102895 to your threat-intel watchlist, enable alerts for any IOCs that reference gpustack, and monitor your feed for any new reports linking this flaw to active campaigns. CISA’s listing says exploitation is happening, not who is behind it, so treat any group name you see as someone’s claim. Action: Register the CVE in your intel platform and set up automated notifications.