BerriAI · LiteLLM · published 2026-09-02

CVE-2026-84377LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-84377 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 46% of all CVEs. This LiteLLM vulnerability: CVSS 6.5 (v3.1). Fixed upstream in LiteLLM 1.96.2, 1.95.1, 1.94.3, 1.93.2 (+6 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in LiteLLM 1.96.2, 1.95.1, 1.94.3, 1.93.2, 1.92.2, 1.91.5, 1.90.7, 1.89.7, 1.88.6, 1.83.9.

Patch events

  1. This monthSecurity release

    AI toolingLiteLLM

    LiteLLM security fixes: 2 CVEs

    Upgrade to 1.96.21.95.11.94.31.93.21.92.21.91.51.90.71.89.71.88.61.83.9

    Why: Vendor security release for server software (most severe: CVE-2026-84377).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.5% (46th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to versions 1.88.6 and 1.96.2, any authenticated LiteLLM proxy user could redirect an outbound provider call to a destination the user controls and cause the proxy to send its configured provider credentials to that destination. Request validation in litellm/proxy/auth/auth_utils.py, litellm/proxy/common_request_processing.py, litellm/proxy/health_endpoints/_health_endpoints.py, litellm/proxy/image_endpoints/endpoints.py, and litellm/proxy/litellm_pre_call_utils.py used incomplete checks that did not cover every sensitive parameter or inspect equivalent values across nested request fields, path values, and bracket-notation form data. Routing and credential parameters including api_base, base_url, model_list, fallbacks, and litellm_credential_name could therefore be applied without clearing the operator's stored key, exposing upstream provider credentials and other configured secrets and permitting server-side requests to internal services reachable by the proxy. This issue is fixed in versions 1.88.6 and 1.96.2.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →