Exclude backdoored litellm 1.107.0 (Oct 2026 supply-chain compromise)
Merged
MI
1mo ago+3+3+0123456789-2-2-0123456789
What happened
litellm 1.107.0 was published to PyPI and Docker in a compromised (backdoored) form on 2026-10-21. The last safe release is 1.106.2.
- LiteLLM incident report: https://docs.litellm.ai/blog/security-incident-oct-21-2026
- Socket analysis: https://socket.dev/blog/litellm-compromise
This repo had no guard against the March 2026 compromise (1.82.7/1.82.8) either. We never locked any of these versions: uv.lock stays at litellm 1.70.0.
What this changes
pyproject.toml:litellm>=1.70.0becomeslitellm>=1.70.0,!=1.82.7,!=1.82.8,!=1.107.0, with a one-line comment citing both incidents.uv.lock: only the litellm specifier line in the project metadata changes. No other dependency changes.
Verification
uv lock --checkpasses.uv lock --dry-run --upgrade-package litellmresolves to 1.106.2, not 1.107.0.- This repo has no
make citarget, so I ran the individual checks:make vulturepasses.black --checkpasses.make testfails at collection becauseDEV_ENVand the other secrets are missing in this sandbox. It fails the same way onmain.
- No pre-commit hooks are installed in this repo, so none were skipped.
Generated by Claude Code
Summary by cubic
Prevents dependency resolution from ever picking the compromised litellm 1.107.0 (and the previously missed 1.82.7/1.82.8 releases). The locked version is unchanged at 1.70.0.
- Updates the
litellmspecifier inpyproject.tomlanduv.lockto exclude 1.82.7, 1.82.8, and 1.107.0, with a comment citing both incidents. uv lock --checkpasses anduv lock --dry-run --upgrade-package litellmresolves to 1.106.2.