CVE-2026-31214: ml-engineering · CVE-2026-31214 is a critical
Affects ml-engineeringSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubstas00/ml-engineeringpkg:github/stas00/ml-engineeringOther 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
Until an official fix is available, users should avoid loading untrusted PyTorch checkpoint files with this script or modify the script to use torch.load() with the weights_only=True parameter to restrict deserialization to tensor weights only.
Description
CVE-2026-31214 is a critical vulnerability in the torch-checkpoint-shrink.py script of the ml-engineering project. The script insecurely deserializes PyTorch checkpoint files using torch.load() without the security-restrictive weights_only=True parameter. This allows an attacker to craft malicious checkpoint files that, when loaded, can execute arbitrary code in the context of the user running the script. The vulnerability is due to unsafe deserialization (CWE-502) via Python's pickle module. There is no official patch or remediation guidance currently available.