Active exploitation (CISA KEV) of an auth-bypass RCE in an AI GPU cluster manager enabling admin takeover, secret exfiltration and code execution — high-risk for organizations running AI infra.
CVE-2026-102895
Auth bypass in GPUStack allows unauthenticated admin access and remote code execution.
do firstApply 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). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Is CVE-2026-102895 being exploited?
Yes. CVE-2026-102895 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-102895?
CVE-2026-102895 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102895?
Yes. A fix has been recorded for CVE-2026-102895. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102895 affect?
CVE-2026-102895 affects GPUStack < 2.2.0 (observed on 2.1.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102895?
Upgrade to GPUStack v2.2.0 immediately; block internet access and rotate exposed keys/secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can gain admin, create persistent API keys, modify users/models, exfiltrate cloud/worker secrets, and achieve RCE via POST /v2/inference-backends/from-yaml.
Immediate action required
- affected< 2.2.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 5 Nov 2026 (SSVC 2.0.3).
timeline
- 4 Nov 2026Published
- 5 Nov 2026CISA SSVC assessment: exploitation active · same day later
- 9 Nov 2026Added to CISA KEV (exploited in the wild) · 4 days later
- 10 Nov 2026CVE record last updated · 1 day later
- 10 Nov 2026Analysed by vulneraibility.com · same day later
- 12 Nov 2026CISA remediation due date (US federal agencies) · 1 day later
also known as
- Linkgithub.com /gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr
- Linkgithub.com /gpustack/gpustack/pull/5346
- Linkgithub.com /gpustack/gpustack/commit/53f42a6a553542974396d16a4ff6b12bcbedb48d
- Linkgithub.com /gpustack/gpustack/releases/tag/v2.2.0
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102895
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.