Pin lightning <=2.6.1 to avoid CVE in 2.6.2/2.6.3#12
Merged
Conversation
PyTorch Lightning 2.6.2 and 2.6.3 contain a security vulnerability. Cap the upper bound so fresh installs don't resolve to affected releases while preserving the existing >=2.0 floor. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Caps the lightning dependency to avoid resolving to vulnerable PyTorch Lightning releases while keeping the existing lower bound, preventing fresh installs from pulling affected versions.
Changes:
- Update
lightningdependency constraint from>=2.0to>=2.0,<=2.6.1.
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.
PyTorch Lightning 2.6.2 and 2.6.3 contain a security vulnerability. Cap the upper bound so fresh installs don't resolve to affected releases while preserving the existing >=2.0 floor.
Change: "lightning>=2.0" → "lightning>=2.0,<=2.6.1" in pyproject.toml
Note: Revisit once a patched release (≥2.6.4 or new minor/major) ships — the upper bound can then be relaxed or converted to an exclusion range (!=2.6.2,!=2.6.3).