CVE-2026-102895
CVE-2026-102895 is a security flaw in GPUStack. Attackers can run their own code on GPUStack from anywhere, without logging in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 9 Nov 2026.[1]
GPUStack is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. GPUStack has published a fix or advice.
Description
CISA calls it an improper authentication in GPUStack GPUStack. In its words: “GPUStack contains an improper authentication vulnerability which could allow unauthenticated administrative access, including user and model changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/from-yaml.”[1]
The CVE record adds: “GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning. Prior to 2.2.0, get_current_user in gpustack/api/auth.py treated a loopback request source as the built-in administrator when force_auth_localhost was false, which was the default. A remote request could appear to originate from 127.0.0.1 because client_ip_getter accepted a same-host reverse proxy peer or a client-supplied X-GPUStack-Real-IP loopback value. The bypass allowed unauthenticated administrative access, including user and model changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/from-yaml. Exploitation was observed in the wild against a 2.1.1 deployment. This issue is fixed in version 2.2.0.”[2]
The underlying weakness is improper authentication (CWE-287), authentication bypass by spoofing (CWE-290), CWE-346, in MITRE’s list of common software weaknesses.
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; GPUStack’s advisory has them[3]. CISA names the product as GPUStack GPUStack.
Most families won’t have GPUStack; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 9 Nov 2026, 5 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 12 Nov 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 6%. That’s in the top 7% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
GPUStack has published a fix or advice.[3] CISA’s required action: “Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).”[1]
- Check whether you use it.GPUStack is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 12 Nov 2026 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 6%.[4] |
See also
Other improper authentication flaws
- CVE-2024-27834, Apple devices: improper authentication ·
- CVE-2026-105133, AhsayCBS: improper authentication ·
- CVE-2026-42018, JFrog Artifactory: improper authentication ·
- CVE-2026-82329, JFrog Artifactory: improper authentication ·
- CVE-2026-59822, BerriAI LiteLLM: improper authentication ·
Added the same day
- CVE-2026-123218, IBM Aspera Faspex: incorrect authorization ·
- CVE-2026-123158, OpenBSD OpenSSH: unexpected status code or return value ·
- CVE-2026-116779, SignalWire FreeSwitch: code injection ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “GPUStack Improper Authentication Vulnerability”. Known Exploited Vulnerabilities Catalog, added 9 Nov 2026.
- ^ National Institute of Standards and Technology. “CVE-2026-102895 Detail”. National Vulnerability Database, published 4 Nov 2026.
- ^ GPUStack. Advisories and fixes: github.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.057, percentile 93.2, 19 Nov 2026.
- CVE Program. “CVE-2026-102895”. The official CVE record.
This article is built from CISA’s catalog (version 2026.11.18), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.

