ETK-2026-2654Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-g665-42m7-mgcv ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
pip:gpustack >=2.2.0; <2.3.0
fixed in 2.3.0
ETK-2026-2654Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/gpustack
3h 46msince last run
48mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −17h16mwaiting for further signals−3h46m
−12h
−6h
0

description

gpustack versions before 2.3.0 do not properly enforce cluster boundaries when processing worker registrations. An attacker with a worker registration token for any cluster may alter registrations in another cluster, potentially redirecting workloads or accessing that cluster's resources.

mitigation

Upgrade gpustack to version 2.3.0 or later. Until upgraded, limit management API network access and treat worker registration tokens as privileged credentials.

fixed in 2.3.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
48m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-26 01:37Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2654

{
  "etk_id": "ETK-2026-2654",
  "cve_id": null,
  "display_id": "ETK-2026-2654",
  "ghsa_id": "GHSA-g665-42m7-mgcv",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-cluster authorization bypass in gpustack worker registration",
  "summary": "gpustack versions before 2.3.0 do not properly enforce cluster boundaries when processing worker registrations. An attacker with a worker registration token for any cluster may alter registrations in another cluster, potentially redirecting workloads or accessing that cluster's resources.",
  "mitigation": "Upgrade gpustack to version 2.3.0 or later. Until upgraded, limit management API network access and treat worker registration tokens as privileged credentials.",
  "vendor": "pip",
  "product": "pip:gpustack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=2.2.0",
        "<2.3.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.3.0"
      ],
      "package_name": "gpustack",
      "purl": "pkg:pypi/gpustack"
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 47.6495638,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T01:37:41+00:00",
      "days": -0.7195922331018518,
      "is_lower_bound": true,
      "measured_at": "2026-10-26T18:53:53.797582+00:00",
      "url": "https://github.com/gpustack/gpustack/security/advisories/GHSA-g665-42m7-mgcv"
    }
  }
}

published 2026-10-26 14:42Z
last change 2026-10-26 18:41Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.