CVE-2026-114612

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

GHSA-7hp6-4w63-5g45 ↗EUVD-2026-108277 ↗

no check availablenot proven exploitable
cve.orgpublic 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.91.0, < 1.100.4; >= 1.101.0, < 1.101.3; >= 1.102.0, < 1.102.2; >= 1.103.0; <1.103.1; >= 1.104.0rc1, < 1.104.0rc2
fixed in 1.100.4, 1.101.3, 1.102.2, 1.103.1, 1.104.0rc2
CWE-269 Improper Privilege Management
ETK-2026-2489Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/litellm
1h 35msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h53m
0
+4h
+6h
+8h
+10h
+12h

description

LiteLLM proxy releases from 1.87.0 until the applicable patched release can allow an authenticated internal user to obtain proxy-administrator privileges. An attacker with that access can execute commands through the MCP stdio capability. Releases 1.87.0 through 1.90.x are affected only when EXPERIMENTAL_UI_LOGIN is enabled; later affected releases are exposed in the default configuration.

mitigation

Upgrade LiteLLM to 1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0rc2, as appropriate for the release line. Until upgrading, set EXPERIMENTAL_UI_LOGIN=false to disable the affected login path.

fixed in 1.100.4, 1.101.3, 1.102.2, 1.103.1, 1.104.0rc2

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
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 18:01Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-22 18:01Z
  2. 2026-10-22 18:01Z

this entry in the feed

GET /api/v1/feed/CVE-2026-114612

{
  "etk_id": "ETK-2026-2489",
  "cve_id": "CVE-2026-114612",
  "display_id": "CVE-2026-114612",
  "ghsa_id": "GHSA-7hp6-4w63-5g45",
  "euvd_id": "EUVD-2026-108277",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Privilege escalation through cryptographic key reuse in LiteLLM",
  "summary": "LiteLLM proxy releases from 1.87.0 until the applicable patched release can allow an authenticated internal user to obtain proxy-administrator privileges. An attacker with that access can execute commands through the MCP stdio capability. Releases 1.87.0 through 1.90.x are affected only when EXPERIMENTAL_UI_LOGIN is enabled; later affected releases are exposed in the default configuration.",
  "mitigation": "Upgrade LiteLLM to 1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0rc2, as appropriate for the release line. Until upgrading, set EXPERIMENTAL_UI_LOGIN=false to disable the affected login path.",
  "vendor": "pip",
  "product": "pip:litellm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.91.0, < 1.100.4"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.100.4"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.101.0, < 1.101.3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.101.3"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.102.0, < 1.102.2"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.102.2"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.103.0",
        "<1.103.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.103.1"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.104.0rc1, < 1.104.0rc2"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "1.104.0rc2"
      ],
      "package_name": "litellm",
      "purl": "pkg:pypi/litellm"
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/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": 16.684169316666665,
  "t0_at": "2026-10-22T18:01:52.768000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T18:01:52.768000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T18:01:52.768000+00:00",
      "url": "https://github.com/BerriAI/litellm/security/advisories/GHSA-7hp6-4w63-5g45"
    }
  }
}

published 2026-10-22 19:38Z
last change 2026-10-22 21:20Z

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.