MediumGHSA-3cv6-jpf6-8222CVE-2026-84377PYSEC-2026-4066

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

Published 30 Sept 2026 · Updated 1 Oct 2026

Is your project on an affected litellm?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<1.88.6
Fixed in
1.88.6
Update to the fixed version for your release line, for example:pip install 'litellm>=1.88.6'
Affected
>=1.89.0 <1.89.7
Fixed in
1.89.7
Update to the fixed version for your release line, for example:pip install 'litellm>=1.89.7'
Affected
>=1.90.0 <1.90.7
Fixed in
1.90.7
Update to the fixed version for your release line, for example:pip install 'litellm>=1.90.7'
Affected
>=1.91.0 <1.91.5
Fixed in
1.91.5
Update to the fixed version for your release line, for example:pip install 'litellm>=1.91.5'
Affected
>=1.92.0 <1.92.2
Fixed in
1.92.2
Update to the fixed version for your release line, for example:pip install 'litellm>=1.92.2'
Affected
>=1.93.0 <1.93.2
Fixed in
1.93.2
Update to the fixed version for your release line, for example:pip install 'litellm>=1.93.2'
Affected
>=1.94.0 <1.94.3
Fixed in
1.94.3
Update to the fixed version for your release line, for example:pip install 'litellm>=1.94.3'
Affected
>=1.95.0 <1.95.1
Fixed in
1.95.1
Update to the fixed version for your release line, for example:pip install 'litellm>=1.95.1'
Affected
>=1.96.0 <1.96.2
Fixed in
1.96.2
Update to the fixed version for your release line, for example:pip install 'litellm>=1.96.2'

Details

Impact

Any authenticated LiteLLM proxy user could redirect an outbound provider call to a destination they control and cause the proxy to send its own configured provider credentials to that destination. The proxy's request-body validation was a denylist that did not cover every sensitive parameter and did not inspect parameters nested inside other request fields, so a caller could supply a routing or credential value that the proxy applied without clearing the operator's stored key. Any authenticated user could therefore exfiltrate the operator's upstream provider credentials and other configured secrets, and perform Server-Side Request Forgery against internal services reachable from the proxy.

Patches

Fixed in 1.96.2, 1.95.1, 1.94.3, 1.93.2, 1.92.2, 1.91.5, 1.90.7, 1.89.7, and 1.88.6.

Workarounds

Set general_settings.allow_client_side_credentials to false so callers cannot override connection parameters, restrict proxy keys to trusted callers, and block the affected parameters (api_base, base_url, model_list, fallbacks, provider credential fields) at a reverse proxy or API gateway.

Is GHSA-3cv6-jpf6-8222 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected litellm, and gives you the command that fixes it.

More advisories for litellm

  • HighGHSA-g5ff-637f-6q2mLiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials` · 27 Oct 2026
  • MediumGHSA-hhww-mrg2-969hLiteLLM vulnerable to reflected XSS in /sso/debug/callback · 27 Oct 2026
  • HighCVE-2026-114612LiteLLM: Privilege Escalation to Proxy Admin via Cross-Domain Reuse of the Salt Key · 27 Oct 2026
  • MediumCVE-2026-59823LiteLLM Proxy has server-side request forgery via the `user_config` request parameter · 17 Sept 2026
  • CriticalCVE-2026-37004LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint · 27 Aug 2026
  • LowCVE-2026-59821LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks · 22 Jul 2026
All 45 advisories for litellm

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.