VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

torch: vulnerability history, versions and safety

torch is a package in the PyPI ecosystem. Vulert records 44 vulnerabilities for it across 51 releases, from Nov 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
44 vulnerabilities recorded C3 H2 M3 L5 U31
i
17 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all torch vulnerabilities

Vulert verdict on torch 2.14.1 i

Updated on 23 Oct 2026

Careful: 2.14.1 has 20 known vulnerabilities, and 17 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.14.1 — affected i
  • Vulnerabilities on record 44 over 3 years · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 17 i
  • Depended on by 25,951 packages i
  • Stars 104,948 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSL-1.0 AND MIT AND Apache-2.0 WITH LLVM-exception i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for torch, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.14.1 30 Sep 2026 C1 M2 L3 U14 Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSL-1.0 AND MIT AND Apache-2.0 WITH LLVM-exception No Details →
2.14.0 02 Sep 2026 C1 M2 L3 U14 Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSL-1.0 AND MIT AND Apache-2.0 WITH LLVM-exception No Details →
2.13.0 08 Jul 2026 C1 M2 L3 U14 Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSL-1.0 AND MIT AND Apache-2.0 WITH LLVM-exception No Details →
2.12.1 17 Jun 2026 C1 M2 L3 U14 BSD-3-Clause No Details →
2.12.0 13 May 2026 L1 U11 BSD-3-Clause No Details →
2.11.0 23 Mar 2026 L1 U11 BSD-3-Clause No Details →
2.10.0 21 Jan 2026 L1 U11 BSD-3-Clause No Details →
2.9.1 12 Nov 2025 L2 U12 BSD-3-Clause No Details →
2.9.0 15 Oct 2025 M1 L2 U12 BSD-3-Clause No Details →
2.8.0 06 Aug 2025 M1 L2 U15 BSD-3-Clause No Details →
2.7.1 04 Jun 2025 M2 L2 U16 BSD-3-Clause No Details →
2.7.0 23 Apr 2025 M2 L3 U20 BSD-3-Clause No Details →
2.6.0 29 Jan 2025 M3 L5 U25 BSD-3-Clause No Details →
2.5.1 29 Oct 2024 C1 M3 L5 U22 BSD-3-Clause No Details →
2.5.0 17 Oct 2024 C1 M3 L5 U22 BSD-3-Clause No Details →
2.4.1 04 Sep 2024 C1 M3 L5 U23 BSD-3-Clause No Details →
2.4.0 24 Jul 2024 C1 M3 L5 U23 BSD-3-Clause No Details →
2.3.1 05 Jun 2024 C2 M3 L5 U23 BSD-3-Clause No Details →
2.3.0 24 Apr 2024 C2 M3 L5 U23 BSD-3-Clause No Details →
2.2.2 27 Mar 2024 C2 M3 L5 U23 BSD-3-Clause No Details →
2.2.1 22 Feb 2024 C2 M3 L5 U23 BSD-3-Clause No Details →
2.2.0 30 Jan 2024 C2 M3 L5 U23 BSD-3-Clause No Details →
2.1.2 14 Dec 2023 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
2.1.1 15 Nov 2023 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
2.1.0 04 Oct 2023 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
2.0.1 08 May 2023 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
2.0.0 15 Mar 2023 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
1.13.1 15 Dec 2022 C2 H2 M3 L5 U26 BSD-3-Clause No Details →
1.13.0 28 Oct 2022 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.12.1 05 Aug 2022 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.12.0 28 Jun 2022 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.11.0 10 Mar 2022 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.10.2 27 Jan 2022 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.10.1 15 Dec 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.10.0 21 Oct 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.9.1 20 Sep 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.9.0 15 Jun 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.8.1 25 Mar 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.8.0 04 Mar 2021 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.7.1 10 Dec 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.7.0 27 Oct 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.6.0 28 Jul 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.5.1 18 Jun 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.5.0 21 Apr 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.4.0 15 Jan 2020 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.3.1 07 Nov 2019 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.3.0 10 Oct 2019 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.2.0 08 Aug 2019 C3 H2 M3 L5 U27 BSD-3-Clause No Details →
1.1.0 30 Apr 2019 C3 H2 M3 L5 U27 — No Details →
1.0.1 05 Feb 2019 C3 H2 M3 L5 U27 — No Details →
1.0.0 07 Dec 2018 C3 H2 M3 L5 U27 — No Details →

All 51 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 6
  • 2025 33
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 44 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for torch

The 5 most severe of 44 vulnerabilities recorded for this package

Search all 44 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-45907: PyTorch Arbitrary Code Execution 9.8 critical 1.13.1 26 Nov 2022
CVE-2025-32434: PyTorch Remote Command Execution Vulnerability in torch.load 9.8 critical 2.6.0 18 Apr 2025
CVE-2024-48063: PyTorch RemoteModule Deserialization RCE Vulnerability 9.8 critical 2.5.0 29 Oct 2024
CVE-2024-7804: PyTorch Remote Code Execution Vulnerability Due to Deserialization Flaw 9.8 critical No fix published 20 Mar 2025
CVE-2025-32434: PyTorch Remote Code Execution Vulnerability via torch.load with weights_only=True 9.3 critical 2.6.0 18 Apr 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About torch

Is torch safe to use?

Vulert records 44 vulnerabilities for torch in PyPI: 3 critical, 2 high, 3 medium and 5 low, plus 31 not yet rated. 17 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is torch's Vulert package health score?

Vulert scores torch 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of torch affected?

Yes. 2.14.1, the version you would install today, has 20 known vulnerabilities, and 17 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of torch should I use?

2.14.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does torch have?

44 vulnerabilities are recorded for torch in the PyPI ecosystem: 3 critical, 2 high, 3 medium and 5 low, plus 31 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new torch vulnerabilities disclosed?

4 vulnerabilities were recorded for torch in the last 12 months, and the oldest entry in this database dates to 26 Nov 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of torch are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor torch for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the torch version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.