{"answers":{"affected":"1 open source package ship an affected version, including gpustack. It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-102895 in the wild since at least 9 Nov 2026.","exposure":"","fix":"Upgrade gpustack to 2.2.0 or later. US federal agencies must fix it by 12 Nov 2026.","what":"CVE-2026-102895 is a critical vulnerability in gpustack, published on 4 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-102895 and fix it if it is affected.\n\nWhat it is: CVE-2026-102895 is a critical vulnerability in gpustack, published on 4 Nov 2026. \nExploitation: Yes. Attackers have exploited CVE-2026-102895 in the wild since at least 9 Nov 2026.\n\nAffected packages and fixed versions:\n- gpustack (PyPI): affected all versions; fixed in 2.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102895/ (Markdown: https://insights.sbomify.com/CVE-2026-102895/index.md)","id":"CVE-2026-102895","markdown":"https://insights.sbomify.com/CVE-2026-102895/index.md","name":"CVE-2026-102895","record":{"aliases":["GHSA-gj9m-f8ph-pmhr"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"name":"Gpustack","product":"gpustack","vendor":"gpustack"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":true,"headline":"GPUStack Improper Authentication","id":"CVE-2026-102895","indexable":true,"kev":{"dateAdded":"2026-11-09","dueDate":"2026-11-12","knownRansomwareCampaignUse":"Unknown","product":"GPUStack","requiredAction":"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). 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.","vendorProject":"GPUStack","vulnerabilityName":"GPUStack Improper Authentication Vulnerability"},"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Sentry: Improper authentication on SAML SSO process allows user identity linking","id":"CVE-2026-102899"},"nickname":null,"packages":[{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"gpustack","purl":null,"source":"GHSA-gj9m-f8ph-pmhr"}],"prev":{"headline":"GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover","id":"CVE-2026-102894"},"products":["gpustack"],"published":"2026-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-10","vendors":["gpustack"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-102895/"}