fix: pin liteLLM upper bound to 1.82.6 to mitigate supply chain attack#1649
Closed
gn00295120 wants to merge 1 commit intoNVIDIA:mainfrom
Closed
fix: pin liteLLM upper bound to 1.82.6 to mitigate supply chain attack#1649gn00295120 wants to merge 1 commit intoNVIDIA:mainfrom
gn00295120 wants to merge 1 commit intoNVIDIA:mainfrom
Conversation
liteLLM versions 1.82.7 and 1.82.8 were compromised via a supply chain attack. Pin the upper bound to <=1.82.6 (last known safe version) in both requirements.txt and pyproject.toml. Closes NVIDIA#1648 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR mitigates a reported supply-chain compromise in litellm by preventing dependency resolution to the affected releases, aligning the project’s install dependencies with a known-safe upper bound.
Changes:
- Cap
litellmto<=1.82.6(while preserving the existing>=1.68.1lower bound) inrequirements.txt. - Apply the same
litellmupper bound inpyproject.tomlproject dependencies.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| requirements.txt | Adds an upper-bound constraint to prevent installing compromised litellm versions via pip -r. |
| pyproject.toml | Adds the same upper-bound constraint for package installs via PEP 621 dependencies. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #1648
liteLLM versions 1.82.7 and 1.82.8 were compromised by the TeamPCP hacking group via a supply chain attack through a malicious Trivy dependency. The current constraint
litellm>=1.68.1allows pip to resolve and install these compromised versions.What the malicious versions do
.pthfile insite-packagesthat re-executes the payload on every Python startup, surviving package upgrades and reinstallsFix
This PR caps the liteLLM dependency at
<=1.82.6(the last known safe version) in both:requirements.txtpyproject.tomlThe constraint is now
litellm>=1.68.1,<=1.82.6, preventing pip from pulling the compromised versions while maintaining the existing lower bound.References