fix: pin liteLLM <=1.82.6 to mitigate TeamPCP supply chain attack

[gn00295120]

Summary

liteLLM versions 1.82.7 and 1.82.8 were compromised by the TeamPCP group via a supply chain attack through Trivy. The current dependency constraint allows these malicious versions to be installed.

Impact

The compromised versions steal sensitive credentials including SSH keys, AWS/GCP/K8s credentials, CI/CD tokens, and environment variables. Version 1.82.8 installs a .pth persistence mechanism that executes on every Python startup — even after liteLLM is uninstalled.

Fix

This PR pins the upper bound of the liteLLM dependency to <=1.82.6, which is the last known safe version before the compromise. Once BerriAI publishes a verified clean release, this upper bound can be raised.

Files changed (2 pyproject.toml manifests):

• training/rollout/pyproject.toml: >=1.65.0 → >=1.65.0, <=1.82.6
• evaluation/tau2-bench/pyproject.toml: >=1.65.0 → >=1.65.0, <=1.82.6

Note: requirements.txt already pins litellm==1.76.0 (safe). The pdm.lock files resolve to 1.65.1 (safe), but the manifests allowed unbounded upgrades.

References

• BerriAI/litellm#24512 — Incident report
• Wiz.io Analysis — Attack chain analysis
• OSV: MAL-2026-2144 — Advisory

[Copilot]

Pull request overview

Pins the litellm dependency in two Python subprojects to prevent installation of compromised upstream releases, mitigating the referenced supply chain incident.

Changes:

• Add an upper bound (<=1.82.6) to the litellm dependency constraint in training/rollout.
• Add the same upper bound to the litellm dependency constraint in evaluation/tau2-bench.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
training/rollout/pyproject.toml	Constrains litellm to known-safe versions by adding an upper bound.
evaluation/tau2-bench/pyproject.toml	Applies the same litellm upper-bound constraint to the bench project manifest.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.