Skip to content

[High] Patch pytorch for CVE-2026-34445, CVE-2026-34446#16649

Draft
aninda-al wants to merge 2 commits intomicrosoft:fasttrack/2.0from
Kanishk-Bansal:pytorch/2.0/cve-2026-34446
Draft

[High] Patch pytorch for CVE-2026-34445, CVE-2026-34446#16649
aninda-al wants to merge 2 commits intomicrosoft:fasttrack/2.0from
Kanishk-Bansal:pytorch/2.0/cve-2026-34446

Conversation

@aninda-al
Copy link
Copy Markdown
Contributor

@aninda-al aninda-al commented Apr 13, 2026

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?
Patch pytorch for
CVE-2026-34445 (MEDIUM),
Upstream link: https://github.com/onnx/onnx/commit/e30c6935d67cc3eca2fa284e37248e7c0036c46b.patch
Patch backported? Yes

CVE-2026-34446 (HIGH).
Upstream link: https://github.com/onnx/onnx/commit/4755f8053928dce18a61db8fec71b69c74f786cb.patch
Patch backported? Yes

Change Log
Does this affect the toolchain?

NO

Associated issues
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging fasttrack/2.0 PRs Destined for Azure Linux 2.0 labels Apr 13, 2026
@Kanishk-Bansal Kanishk-Bansal changed the title [High] Patch for CVE-2026-34445, CVE-2026-34446 [High] Patch pytorch for CVE-2026-34445, CVE-2026-34446 Apr 13, 2026
Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CVE-2026-34446.patch doesn't exist in the spec folder

@aninda-al
Copy link
Copy Markdown
Contributor Author

CVE-2026-34446.patch doesn't exist in the spec folder

My bad, I looked back at the commands and I see that I added CVE-2026-34445.patch twice and git add accepted it. Anyways pushed the missing file.

@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

Build

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

Labels

fasttrack/2.0 PRs Destined for Azure Linux 2.0 Packaging security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants