PyTorch is vulnerable to memory corruption through its torch.jit.script function
CVE-2025-3000 · GHSA-rrmf-rvhw-rf47 · published 2025-03-31 · updated 2026-07-17
- Severity
- Low
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.20%
- Fixed in
- 2.13.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
A vulnerability classified as critical has been found in PyTorch 2.6.0. This affects the function torch.jit.script. The manipulation leads to memory corruption. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.
Upgrade torch to 2.13.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| torch | PyPI | <= 2.12.1 | 2.13.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalPyTorch: `torch.load` with `weights_only=True` leads to remote code executiontorch
- CriticalPyTorch vulnerable to arbitrary code executiontorch
- HighPyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint Filestorch
- HighPyTorch heap buffer overflow vulnerabilitytorch
- HighPytorch use-after-free vulnerabilitytorch
- MediumPyTorch Improper Resource Shutdown or Release vulnerabilitytorch
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.