fix: avoid vulnerable LiteLLM versions#113
Open
DougButdorf wants to merge 3 commits into
Open
Conversation
1cf84ea to
8643604
Compare
|
The current LiteLLM version is causing breaking changes in our systems using this repo. Can we get this reviewed and merged? I see @vineethsai7 has contributed to this repo a lot recently, and @sanket-mendapara as well, maybe they can review? |
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
main.pyproject.toml/uv.lockLiteLLM fix:litellm>=1.83.7,<2, lockfilelitellm==1.83.14.litellm-1.83.0to non-vulnerablelitellm-1.83.14.Why
GitHub advisory GHSA-r75f-5x8p-qvmc / CVE-2026-42208 affects LiteLLM
>=1.81.16, <1.83.7. The formula resource was still vendoring1.83.0, which is inside that range.Verification
pyproject.toml,uv.lock, orFormula/skill-scanner.rb.uv run --python 3.13 pytest -q1300 passed, 5 skipped, 20 warnings.