[Snyk] Security upgrade torch from 1.13.1 to 2.9.0

[robjlyons]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• stable_baselines_3/requirements.txt

⚠️ Warning

stable-baselines3 1.3.0 requires torch, which is not installed.
gym 0.19.0 has requirement cloudpickle<1.7.0,>=1.2.0, but you have cloudpickle 2.2.1.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

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

Pins torch>=2.9.0 in stable_baselines_3/requirements.txt to mitigate a security issue.

• Dependencies:
  • Add torch>=2.9.0 in stable_baselines_3/requirements.txt to address a vulnerability.

^{Written by Cursor Bugbot for commit 90bf2f4. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: PyTorch 2.x: Legacy Library Incompatibility

Requiring torch>=2.9.0 creates a version incompatibility with stable-baselines3==1.3.0. Version 1.3.0 of stable-baselines3 was released around 2021-2022 for PyTorch 1.x, while PyTorch 2.0+ introduced breaking changes. This mismatch will likely cause runtime failures when stable-baselines3 1.3.0 attempts to use PyTorch 2.9.0 APIs that have changed or been removed since version 1.13.1.