PyPI package

torch 2.12.0 vulnerability, and the version that fixes it

torch 2.12.0 has 1 known vulnerability; 2.13.0 fixes it.

PyPI (opens in a new tab) describes it as “Tensors and Dynamic neural networks in Python with strong GPU acceleration”

Known vulnerabilities
1
None rated high or critical
Released
May 13, 2026
Latest is 2.14.1
Licence
Apache-2.0 AND Apache-2.0 WITH LLVM-exception AND BSD-2-Clause AND BSD-3-Clause AND BSL-1.0 AND MIT
Pulls in
28 packages
Resolved by deps.dev

What to upgrade to

2.13.0 is the closest release with no known vulnerabilities.

  • 2.13.0Upgrade to this

    Fixes the known vulnerability. Released Jul 8, 2026.

    No known vulnerabilities
  • 2.14.1

    Newest 2.x release and the latest release. Released Sep 30, 2026.

    No known vulnerabilities

2.13.0 came out on Jul 8, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates

Findings

Every advisory for torch 2.12.0

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. LowCVE-2025-3000 on OSV.dev (opens in a new tab)GHSA-rrmf-rvhw-rf47EPSS: top 91%

    PyTorch is vulnerable to memory corruption through its torch.jit.script function

    Fixed in 2.13.0. Published Mar 31, 2025.

Is torch the only one?

Paste a public GitHub repo or drop your requirements.txt or pyproject.toml and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly torch 2.12.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and PyPI. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against PyPI, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.