Exclude backdoored litellm 1.107.0 (Oct 2026 supply-chain compromise)

Merged
MI
1mo ago
+3-2

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.

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.0 becomes litellm>=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 --check passes.
  • uv lock --dry-run --upgrade-package litellm resolves to 1.106.2, not 1.107.0.
  • This repo has no make ci target, so I ran the individual checks:
    • make vulture passes.
    • black --check passes.
    • make test fails at collection because DEV_ENV and the other secrets are missing in this sandbox. It fails the same way on main.
  • 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 litellm specifier in pyproject.toml and uv.lock to exclude 1.82.7, 1.82.8, and 1.107.0, with a comment citing both incidents.
  • uv lock --check passes and uv lock --dry-run --upgrade-package litellm resolves to 1.106.2.