CVE-2025-46148: n/a
Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 2.6.1 : update PyTorch when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- PyTorch prior to 2.6.1
- Patch
- Available – fixed in 2.6.1
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 2026-10-26.
What to do
AI-suggested
A fix is available in PyTorch version 2.6.1. Users should upgrade to version 2.6.1 or later to resolve the incorrect result issue in nn.PairwiseDistance(p=2) when using eager mode.
Description
A vulnerability in PyTorch versions prior to 2.6.1 causes the nn.PairwiseDistance(p=2) function to produce incorrect results when used in eager mode.