How to Fix CVE-2026-102895 in Gpustack

The two-minute check

1. Open the Gpustack web interface you use to manage your GPU cluster.
2. Look at the version number, usually shown on a settings or about page.
3. Check whether it is version 2.1.1 or earlier, since that is the build known to be attacked.
4. Check whether a setting called force_auth_localhost has ever been turned on. If no one has touched it, it is almost certainly off.

When you can stop reading

If your business has never installed Gpustack, you are not affected and can close this tab. If you have no GPU cluster and no AI model-serving infrastructure running this software, this flaw has nothing to work with on your network.

What the official record says

This flaw carries a Common Vulnerability Scoring System (CVSS) score of 9.8, rated CRITICAL (NVD). The scoring details show an attacker needs no account, no password, and no click from anyone inside your business. They only need network access to the system running Gpustack. The flaw lets a remote request impersonate a trusted "localhost" connection, the kind of request the software was built to automatically treat as an administrator.

The Exploit Prediction Scoring System (EPSS) gives this flaw a probability of 0.00555, or 0.56%, placing it at the 46.664th percentile of all scored vulnerabilities (FIRST.org). EPSS is a forecast of how likely exploitation is in the next 30 days. It is not a measure of how damaging the flaw would be if exploited, which is a separate question answered by the CVSS score above.

This issue is already confirmed on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning criminals are already using it in real attacks (CISA KEV). The record notes exploitation was observed against a 2.1.1 deployment.

What that means for a business like yours

An attacker who reaches your Gpustack instance can act as its built-in administrator without logging in at all. The record describes user and model changes, creation of permanent administrator API keys, and disclosure of worker and cloud-provider secrets. It also describes a path to code execution through a specific upload feature. In plain terms: someone outside your business could take over the system and anything connected to it.

If someone else manages your IT

Send your provider a short message. Copy and paste the lines below.

• "We run Gpustack. Please confirm whether it is exposed to CVE-2026-102895."
• "Please update it to version 2.2.0 or later, the version that fixes this."
• "Please confirm force_auth_localhost is enabled, and tell me when it's done."

If you don't already have a managed-IT relationship, LayerLogix's managed IT services team can run this check and the patch for you.

If you manage it yourself

1. Open the vendor's advisory page, which explains the fix in detail (GitHub Security Advisory).
2. Read the release notes for version 2.2.0, the fixed version named in the record (Release notes).
3. Back up your current configuration before changing anything.
4. Install version 2.2.0 or later on every server running Gpustack.
5. Restart the Gpustack service once the update finishes.
6. Confirm the setting force_auth_localhost is now enabled, since the default was the problem.

The honest answer is now. This flaw is on the CISA Known Exploited Vulnerabilities catalog, with a federal due date of November 12, 2026 for government systems (CISA KEV). Your business isn't bound by that federal deadline, but the exploitation it reflects is already happening. There is no reason to wait.

Don't just trust an installer's progress bar. Open the Gpustack interface again after updating and confirm the version number reads 2.2.0 or later. Then check the force_auth_localhost setting directly in the configuration and confirm it shows as enabled, not just that the update completed. If you have access to logs, review the patch commit to understand exactly what changed in the authentication code (patch commit).

If you cannot update immediately, enable force_auth_localhost as an interim step. This closes the specific loophole the record describes, where a remote request could impersonate a local, trusted connection. It does not fix every possible issue in the software, so treat it as a bridge, not a replacement for the update.

You can also restrict network access to the Gpustack management interface so only trusted internal addresses can reach it. A properly configured firewall rule or a virtual private network (VPN) requirement buys time, but anyone who already has internal network access is not stopped by it. Neither step replaces installing version 2.2.0. For businesses with sensitive data behind this kind of infrastructure, our cybersecurity services team can help set up these interim controls correctly.

Do I have to do anything if I only run Gpustack for internal testing?

Yes. The record shows exploitation worked through normal network requests, not through any special production configuration. A test environment with network access is still reachable.

Will updating Gpustack break anything?

The record doesn't say. Back up your configuration before updating, and review the release notes for version 2.2.0 so you know what changed before you apply it.

How do I know if we were already attacked before patching?

The record mentions administrator API-key creation and secret disclosure as outcomes of this flaw. Check your Gpustack admin account list and API keys for anything you don't recognize, and rotate any cloud-provider credentials stored in the system.

Does this affect other software we run, like tools covered by HIPAA or FTC Safeguards Rule requirements?

The record only names Gpustack. If Gpustack handles data covered by rules like HIPAA or the FTC Safeguards Rule, treat this patch as part of your required safeguards, not a separate task.

Is this something our managed-IT provider should have already caught?

A good provider tracks vendor advisories and the CISA KEV catalog as part of normal operations. If you're not confident your current setup is being watched this closely, a free IT assessment from LayerLogix can tell you where you stand.

LayerLogix brings 20+ years of experience and 100% U.S.-based support to Texas businesses handling exactly this kind of urgent patching work. If you want a second set of eyes on your Gpustack deployment or your broader security posture, contact us today.