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

validatingZero is analyzing and reversing it now.

GHSA-9jmg-hx5p-h592 ↗

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.3
fixed in 2.3.0
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-4230Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/gpustack
–running
startingcurrent stage
timeline
0 = cve.org, not yet published
trigger signal −7h42m
−6h
−4h
−2h
0

description

GPUStack versions before 2.3.0 do not enforce model visibility when authenticated organization owners create benchmarks. Such a user may retrieve another organization's model deployment configuration in a benchmark snapshot, including fields that can contain credentials.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade gpustack to version 2.3.0 or later. Until upgraded, block POST /v2/benchmarks and review existing benchmark snapshots for cross-organization references; remove affected snapshots and rotate any exposed credentials.

fixed in 2.3.0

check
building now
exploit
not yet
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.
–
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
–
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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-11 16:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4230",
  "cve_id": null,
  "display_id": "ETK-2026-4230",
  "ghsa_id": "GHSA-9jmg-hx5p-h592",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "awaiting_cve",
  "title": "Authorization bypass exposes cross-organization configurations in gpustack",
  "summary": "GPUStack versions before 2.3.0 do not enforce model visibility when authenticated organization owners create benchmarks. Such a user may retrieve another organization's model deployment configuration in a benchmark snapshot, including fields that can contain credentials.",
  "mitigation": "Upgrade gpustack to version 2.3.0 or later. Until upgraded, block POST /v2/benchmarks and review existing benchmark snapshots for cross-organization references; remove affected snapshots and rotate any exposed credentials.",
  "vendor": null,
  "product": "pip:gpustack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 2.2.3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.3.0"
      ],
      "package_name": "gpustack",
      "purl": "pkg:pypi/gpustack"
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T16:22:35+00:00",
      "days": -0.3206587183333333,
      "is_lower_bound": true,
      "measured_at": "2026-11-12T00:04:19.957519+00:00",
      "url": "https://github.com/gpustack/gpustack/security/advisories/GHSA-9jmg-hx5p-h592"
    }
  }
}

published 2026-11-11 23:32Z
last change 2026-11-12 00:04Z

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.