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

validatedZero produced an exploit or a check.

GHSA-g5ff-637f-6q2m ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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:litellm <1.95.0
fixed in 1.95.0
CWE-20 Improper Input Validation
ETK-2026-368, no cve assigned
pkg:pypi/litellm
−18dTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0dcheck available+1.2dagent stopped
0
+5d
+10d
+15d
+20d

description

LiteLLM proxy releases before 1.95.0 allow a low-privilege authenticated user to read local files accessible to the proxy process. Exposed credentials or API keys could allow the attacker to gain broader control of the proxy.

mitigation

Upgrade LiteLLM to version 1.95.0 or later.

fixed in 1.95.0

check
available
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.
deterministic
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
24m
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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-01 13:57Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-368",
  "cve_id": null,
  "display_id": "ETK-2026-368",
  "ghsa_id": "GHSA-g5ff-637f-6q2m",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Authenticated arbitrary file read in LiteLLM proxy",
  "summary": "LiteLLM proxy releases before 1.95.0 allow a low-privilege authenticated user to read local files accessible to the proxy process. Exposed credentials or API keys could allow the attacker to gain broader control of the proxy.",
  "mitigation": "Upgrade LiteLLM to version 1.95.0 or later.",
  "vendor": "pip",
  "product": "pip:litellm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<1.95.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.95.0"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 24.440907266666667,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-02T19:30:25.190423+00:00",
      "days": -18.42845255525463,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:23.514395+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-01T13:57:14+00:00",
      "days": -19.65983207403935,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:23.514395+00:00",
      "url": "https://github.com/BerriAI/litellm/security/advisories/GHSA-g5ff-637f-6q2m"
    }
  }
}

published 2026-10-02 19:05Z
last change 2026-10-21 05:31Z

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.