Skip to content

[AutoPR- Security] Patch pytorch for CVE-2025-51480 [HIGH]#17338

Draft
azurelinux-security wants to merge 4 commits into
microsoft:fasttrack/3.0from
azurelinux-security:azure-autosec/pytorch/3.0/1121144
Draft

[AutoPR- Security] Patch pytorch for CVE-2025-51480 [HIGH]#17338
azurelinux-security wants to merge 4 commits into
microsoft:fasttrack/3.0from
azurelinux-security:azure-autosec/pytorch/3.0/1121144

Conversation

@azurelinux-security
Copy link
Copy Markdown
Contributor

@azurelinux-security azurelinux-security commented May 18, 2026

Auto Patch pytorch for CVE-2025-51480.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1121144&view=results

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • N/A
Links to CVEs
Test Methodology

@v-aaditya
Copy link
Copy Markdown
Contributor

Triggered Buddy Build to check if the affected file is being compiled during the package build, by introducing syntax error in affected file through a test patch.

@v-aaditya
Copy link
Copy Markdown
Contributor

CVE-2026-51480

  1. The CVE affects the third-party vendor package onnx as it is in affected range of <= 1.17.1 and the affected files and vulnerable code is present and is getting compiled in current version 1.15.0rcs of pytorch.
    image
  2. The AI patch matches with the upstream patch completely, except the import onnx.checker as onnx_checker has not been included from upstream patch as it is already present in current source.
  3. The AI patch has upstream patch reference.
  4. Buddy Build is successful and the patch applies cleanly (checked build logs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants