chore(deps): update dependency torch to v2.6.0 [security] - autoclosed

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
torch	==2.2.2 -> ==2.6.0

GitHub Vulnerability Alerts

CVE-2025-32434

Description

I found a Remote Command Execution (RCE) vulnerability in PyTorch. When loading model using torch.load with weights_only=True, it can still achieve RCE.

Background knowledge

https://github.com/pytorch/pytorch/security
As you can see, the PyTorch official documentation considers using torch.load() with weights_only=True to be safe.

Since everyone knows that weights_only=False is unsafe, so they will use the weights_only=True to mitigate the seucirty issue.
But now, I just proved that even if you use weights_only=True, it can still achieve RCE.

Credit

This vulnerability was found by Ji'an Zhou.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello! gemini-code-assist here, providing a summary of this pull request. This PR, automatically generated by renovate-bot, aims to update the torch dependency from version 2.2.2 to 2.6.0. The primary motivation for this update is to address a recently disclosed security vulnerability (CVE-2025-32434) in PyTorch related to the torch.load function, even when used with weights_only=True. The changes involve updating the version specification in the requirements.txt file used in the dataflow/run-inference example.

Highlights

• Dependency Update: Updates the torch library dependency.
• Version Bump: Bumps the torch version from 2.2.2 to 2.6.0.
• Security Fix: The update is specifically for security reasons, addressing CVE-2025-32434, a vulnerability in torch.load.

Changelog

• dataflow/run-inference/requirements.txt
  • Updated the specified version of the torch dependency from ==2.2.2 to ==2.6.0.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Dependencies shift,
Security needs a lift,
Code stays safe and swift.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the torch dependency from version 2.2.2 to 2.6.0. This is an important and welcome update as it addresses the security vulnerability CVE-2025-32434, described as a Remote Command Execution (RCE) risk associated with torch.load even when weights_only=True is specified.

The new version 2.6.0 incorporates the necessary patch for this vulnerability (which was fixed in torch 2.3.0 and later versions). The change is confined to the requirements.txt file and is a straightforward version bump. Given the critical nature of the security vulnerability being addressed, this update is highly recommended.

Summary of Findings

• Security Vulnerability Mitigation: This pull request successfully updates the torch dependency to v2.6.0. This version change is critical as it mitigates the Remote Command Execution (RCE) vulnerability identified by CVE-2025-32434.
• Code Change Quality: No new issues of medium, high, or critical severity were identified in the specific code changes introduced by this pull request (i.e., the version update in requirements.txt). The change is precise and directly addresses the intended dependency upgrade.

Merge Readiness

This pull request consists of a crucial security update by upgrading the torch library. The change itself is minimal and correctly applies the version bump. Assuming all continuous integration checks and relevant tests pass successfully, this PR appears ready for merging. While I cannot approve the PR as a reviewer, I strongly recommend its merge to improve the application's security posture. It would be prudent to ensure that any project-specific integration tests for torch 2.6.0 compatibility are green before finalizing the merge.