CVE-2025-32434: PyTorch · `torch.load` with `weights_only=True` leads to remote code execution
Affects pytorchSource GCVE Database
Not known to be exploited : upgrade to 2.6.0 as a priority.
Data as of 26 Oct 2026, 11:07 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.6.0
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade pytorch to 2.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamipytorchpkg:bitnami/pytorchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PyTorch to version 2.6.0 or later, where this vulnerability has been patched. No other mitigation is required as the fix is officially available.
Description
A critical remote code execution vulnerability exists in PyTorch versions prior to 2.6.0 when loading models using torch.load with the weights_only=True parameter. This flaw allows an attacker to execute arbitrary code remotely. The issue has been addressed and patched in PyTorch version 2.6.0.