litellm
45 published advisories; version 1.104.0rc2 or later fixes all but 13 of them.
Compromised releases
1.107.0, 1.82.7, 1.82.8 were published with malicious code. If any of them was installed, remove it, rotate every credential the environment could read, and pin dependencies by hash.
Hit by supply-chain campaigns: LiteLLM release pipeline compromise (1.107.0), LiteLLM PyPI compromise (1.82.7 and 1.82.8).
- Registry
- PyPI
- Advisories
- 45
- Latest fix
- 1.104.0rc2
- Exploited in the wild
- 4
13 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Compromised release. Move to a release the advisory names as clean, and rotate every credential, token and key the environment that ran the affected release could read.GHSA-5mg7-485q-xm76
- Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.GHSA-53gh-p8jc-7rg8 · GHSA-7ggm-4rjg-594w
- Server-side request forgery. Restrict its outbound network access to the hosts it needs, and keep internal addresses and cloud metadata endpoints out of its reach.GHSA-c693-x898-5g4h
- Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.GHSA-j37q-q7p9-vpwm
Check your machine
Finds litellm in your agent and MCP configs, installed skills, global npm packages, the npx and uvx caches, uv and pipx tools, Claude Code and Cursor. It runs offline and sends nothing anywhere.
pip install "shieldpi>=0.10.0"
shieldpi agent-config . --installed3 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- io.github.airas-org/airaslitellm@1.84.0
- io.github.Brightdotdev/darwin-raglitellm@1.83.14
- io.github.hzy9981/aviation-accident-analysislitellm@1.100.1
Source: github.com/berriai/litellm, named in the package metadata (not verified)
3 of the last 10 releases of litellm were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 1.110.0
- 1.108.11
- 1.108.10
- 1.108.9
- 1.106.10
- 1.108.8
- 1.108.7
- 1.109.1
- 1.108.6
- 1.106.9
Green: published with provenance. Grey: without.
OpenSSF Scorecard has not scored this repository.
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].