CVE-2025-46150: PyTorch · CVE-2025-46150 is a medium severity
Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 2.7.0 : update PyTorch when convenient.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- PyTorch before 2.7.0
- Patch
- Available – fixed in 2.7.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 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
Description
CVE-2025-46150 is a medium severity vulnerability in PyTorch versions before 2.7.0. It causes inconsistent results when using the FractionalMaxPool2d operation in conjunction with torch.compile. The issue affects the correctness of computations but does not impact confidentiality, integrity, or availability.