# Backporting CVE fixes from Pytorch v2.6.0 to v2.1.2

**URL:** https://dev-discuss.pytorch.org/t/backporting-cve-fixes-from-pytorch-v2-6-0-to-v2-1-2/2990
**Category:** Uncategorized
**Created:** [May 12, 2025, 2:26pm UTC](https://dev-discuss.pytorch.org/t/backporting-cve-fixes-from-pytorch-v2-6-0-to-v2-1-2/2990 "2025-05-12T14:26:08Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Aman-Surkar](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/aman-surkar/32/2727_2.png) [@Aman-Surkar](https://dev-discuss.pytorch.org/u/Aman-Surkar)
#### Post date: [May 12, 2025, 2:26pm UTC](https://dev-discuss.pytorch.org/t/backporting-cve-fixes-from-pytorch-v2-6-0-to-v2-1-2/2990/1 "2025-05-12T14:26:08Z")

</div>

As per the discussion on issue [Backport CVEs in Pytorch v2.1.2 from Pytorch v2.6.0 · Issue #153370 · pytorch/pytorch](https://github.com/pytorch/pytorch/issues/153370), is [Prevent torch.jit.load path in torch.load when weights\_only=True by mikaylagawarecki · Pull Request #143326 · pytorch/pytorch](https://github.com/pytorch/pytorch/pull/143326) sufficient to backport [CVE-2025-32434](https://github.com/pytorch/pytorch/security/advisories/GHSA-53q9-r3pm-6pq6) in Pytorch v2.1.2?