← back to feed
ETK-2026-2813Zero's internal tracking ID, independent of the CVE number.

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

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

GHSA-w4c7-34wj-hqm8 ↗

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:litellm < 1.103.10; < 1.104.8; < 1.105.6; < 1.106.5
fixed in 1.103.10, 1.104.8, 1.105.6, 1.106.5
CWE-73 External Control of File Name or Path
ETK-2026-2813Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/litellm
cvss10.0cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
2h 02msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+4h33m
0
+2h
+4h
+6h

description

LiteLLM Proxy deployments with Enterprise features enabled are affected. An unauthenticated requester of an LLM route may cause the proxy to expose local-file contents to an external destination, potentially disclosing proxy or provider credentials. Open-source deployments without an Enterprise license are not affected.

mitigation

Upgrade LiteLLM to 1.103.10, 1.104.8, 1.105.6, or 1.106.5, as appropriate for your release line. Until upgraded, restrict proxy egress to approved LLM provider endpoints and require authenticated access to the proxy.

fixed in 1.103.10, 1.104.8, 1.105.6, 1.106.5

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
30m
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-27 20:33Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2813",
  "cve_id": null,
  "display_id": "ETK-2026-2813",
  "ghsa_id": "GHSA-w4c7-34wj-hqm8",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unauthenticated local file disclosure in LiteLLM Enterprise Proxy",
  "summary": "LiteLLM Proxy deployments with Enterprise features enabled are affected. An unauthenticated requester of an LLM route may cause the proxy to expose local-file contents to an external destination, potentially disclosing proxy or provider credentials. Open-source deployments without an Enterprise license are not affected.",
  "mitigation": "Upgrade LiteLLM to 1.103.10, 1.104.8, 1.105.6, or 1.106.5, as appropriate for your release line. Until upgraded, restrict proxy egress to approved LLM provider endpoints and require authenticated access to the proxy.",
  "vendor": "pip",
  "product": "pip:litellm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.103.10"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.103.10"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.104.8"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.104.8"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.105.6"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.105.6"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.106.5"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.106.5"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    }
  ],
  "cwes": [
    73
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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": 30.495469633333332,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T20:33:15+00:00",
      "days": -0.2742645771990741,
      "is_lower_bound": true,
      "measured_at": "2026-10-28T03:08:11.505161+00:00",
      "url": "https://github.com/BerriAI/litellm/security/advisories/GHSA-w4c7-34wj-hqm8"
    }
  }
}

published 2026-10-28 00:39Z
last change 2026-10-28 02:59Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.