VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pytorch: vulnerability history, versions and safety

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

i
45 vulnerabilities recorded U45
i
44 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 22 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pytorch vulnerabilities

Vulert verdict on pytorch i

Updated on 23 Oct 2026

Careful: 44 of the 45 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 45 vulnerabilities on record across 3 years, 4 in the last year.

What to do: Plan around the 44 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 45 over 3 years · 4 in the last year i
  • Latest disclosure 22 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 44 i

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 holds for pytorch, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 44 of 44 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 5
  • 2025 37
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for pytorch

The 5 most severe of 45 vulnerabilities recorded for this package

Search all 45 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Remote Command Execution Vulnerability in PyTorch - CVE-2025-32434 9.8 critical No fix published 18 Apr 2025
Arbitrary Code Execution Vulnerability in PyTorch: CVE-2022-45907 9.8 critical No fix published 26 Nov 2022
Remote Deserialization RCE Vulnerability in PyTorch - CVE-2024-48063 9.8 critical No fix published 29 Oct 2024
Critical Memory Corruption Vulnerability in PyTorch Package 8.8 high No fix published 27 Jan 2026
Critical Memory Corruption Vulnerability in PyTorch 2.6.0+cu124 7.5 high No fix published 10 Mar 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 pytorch

Is pytorch safe to use?

Vulert records 45 vulnerabilities for pytorch in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 45 not yet rated. 44 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does pytorch have?

45 vulnerabilities are recorded for pytorch in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 45 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 pytorch vulnerabilities disclosed?

4 vulnerabilities were recorded for pytorch 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 pytorch 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 pytorch for upcoming vulnerabilities?

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