UTC

torch

13 published advisories; version 2.13.0 or later fixes all but 3 of them.

Registry
PyPI
Advisories
13
Latest fix
2.13.0
Exploited in the wild
None listed

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not torch. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Malicious lookalikes

Packages reported malicious by OpenSSF whose names imitate torch. Check that you install torch itself.

All AI lookalikes →
Provenance

Source: github.com/pytorch/pytorch, named in the package metadata (not verified)

0 of the last 10 releases of torch were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 2.15.0
  • 2.14.1
  • 2.14.0
  • 2.13.0
  • 2.12.1
  • 2.12.0
  • 2.11.0
  • 2.10.0
  • 2.9.1
  • 2.9.0

Green: published with provenance. Grey: without.

OpenSSF Scorecard: 6.4 of 10 on 2022-10-26.

No dangerous CI workflows
10/10
CI tokens read-only by default
Not checked
Build dependencies pinned
Not checked
Branch protection
Not checked
Changes reviewed before merge
10/10
Signed releases
0/10
Actively maintained
10/10
Security policy
10/10
Full Scorecard →

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
PyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint FilesCVE-2026-24747High< 2.10.02.10.02026-01-27
PyTorch: `torch.load` with `weights_only=True` leads to remote code executionCVE-2025-32434Critical< 2.6.02.6.02025-04-18
PyTorch Improper Resource Shutdown or Release vulnerabilityCVE-2025-3730Medium<= 2.7.12.8.02025-04-16
PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence FunctionCVE-2025-2998Medium<= 2.6.0No fix yet2025-03-31
PyTorch is vulnerable to memory corruption through its torch.lstm_cell functionCVE-2025-3001Low< 2.10.02.10.02025-03-31
PyTorch is vulnerable to memory corruption through its torch.jit.script functionCVE-2025-3000Low<= 2.12.12.13.02025-03-31
PyTorch is vulnerable to memory corruption through its unpack_sequence functionCVE-2025-2999Medium< 2.9.12.9.12025-03-31
PyTorch susceptible to local Denial of ServiceCVE-2025-2953Low< 2.7.1-rc12.7.1-rc12025-03-30
PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None ArgumentCVE-2025-2148Low<= 2.6.0No fix yet2025-03-10
PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid ModuleCVE-2025-2149Low<= 2.6.0No fix yet2025-03-10
PyTorch heap buffer overflow vulnerabilityCVE-2024-31580High< 2.2.02.2.02024-04-17
Pytorch use-after-free vulnerabilityCVE-2024-31583High< 2.2.02.2.02024-04-17
PyTorch vulnerable to arbitrary code executionCVE-2022-45907Critical<= 1.13.01.13.12022-11-26

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].