[Snyk] Security upgrade torch from 1.13.1 to 2.9.0#111
[Snyk] Security upgrade torch from 1.13.1 to 2.9.0#111
Conversation
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-TORCH-13052971
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| omegaconf | ||
| compel No newline at end of file | ||
| compel | ||
| torch>=2.9.0 # not directly required, pinned by Snyk to avoid a vulnerability No newline at end of file |
There was a problem hiding this comment.
Bug: Unpinned Dependency Risks Future Stability
The constraint torch>=2.9.0 allows any version 2.9.0 or higher, contradicting the comment claiming it's "pinned". This permits future versions that may reintroduce vulnerabilities or break compatibility. For security fixes, versions are typically pinned to specific versions (e.g., torch==2.9.0) or bounded ranges (e.g., torch>=2.9.0,<3.0.0).
Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):
extra/requirements.txtImportant
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.
Note
Pin torch to >=2.9.0 in extra/requirements.txt to address a security issue.
torchto>=2.9.0inextra/requirements.txtfor security.Written by Cursor Bugbot for commit 0d84ce9. This will update automatically on new commits. Configure here.