Vulnerability · Published Mar 31, 2025 · Assigned by VulDB
CVE-2025-3000PyTorch torch.jit.script memory corruption
Medium 5.3
In plain English
A medium-severity memory corruption in PyTorch. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.2%top 89.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | pytorch | no fix listed | DEBIAN-CVE-2025-3000 |
| Debian:13 | pytorch | no fix listed | DEBIAN-CVE-2025-3000 |
| Debian:14 | pytorch | no fix listed | DEBIAN-CVE-2025-3000 |
| PyPI | torch | 2.13.0 | GHSA-rrmf-rvhw-rf47 |
| PyPI | torch | no fix listed | PYSEC-2025-194 |
| Ubuntu:22.04:LTS | pytorch | no fix listed | UBUNTU-CVE-2025-3000 |
| Ubuntu:25.10 | pytorch | no fix listed | UBUNTU-CVE-2025-3000 |
| Ubuntu:26.04:LTS | pytorch | no fix listed | UBUNTU-CVE-2025-3000 |
| Ubuntu:26.10 | pytorch | no fix listed | UBUNTU-CVE-2025-3000 |
Affected products (as reported)
Weakness: CWE-119 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
References
- VDB-302049 | PyTorch torch.jit.script memory corruption vdb-entry, technical-description
- VDB-302049 | CTI Indicators (IOB, IOC, IOA) signature, permissions-required
- Submit #524197 | pytorch pytorch (torch.jit.script) torch 2.6.0 Segmentation Fault third-party-advisory
- https://github.com/pytorch/pytorch/issues/149623 issue-tracking
- https://github.com/pytorch/pytorch/issues/149623#issue-2935703015 exploit, issue-tracking