CVE-2025-1716
published 2025-02-26CVE-2025-1716: picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI…
PriorityP350critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
1.50%
71.0th percentile
picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via `pip.main()`. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| mmaitre314 | picklescan | < 0.0.22 | 0.0.22 |
| mmaitre314 | picklescan | >= 0 < 0.0.22 | 0.0.22 |
| mmaitre314 | picklescan | >= 0 < 78ce704227c51f070c0c5fb4b466d92c62a7aa3d | 78ce704227c51f070c0c5fb4b466d92c62a7aa3d |
| mmaitre314 | picklescan | >= 0 < 0.0.21 | 0.0.21 |
| mmaitre314 | picklescan | 0.0.1 – 0.0.20 | — |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv4.05.3MEDIUMCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
ghsa5.3MEDIUM
osv5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2025-1716: picklescan before 0
osv·2025-03-03
CVE-2025-1716 CVE-2025-1716: picklescan before 0
picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.
GHSA
Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
ghsa·2025-03-03·CVSS 5.3
CVE-2025-1716 [MEDIUM] CWE-184 Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
### CVE-2025-1716
### Summary
An unsafe deserialization vulnerability in Python’s pickle module allows an attacker to bypass static analysis tools like Picklescan and execute arbitrary code during deserialization. This can be exploited to run pip install and fetch a malicious package, enabling remote code execution (RCE) upon package installation.
### Details
Pickle’s deserialization process allows execution of arbitrary functions via the __reduce__ method. While Picklescan is designed to detect such exploits, this attack evades detection by leveraging pip.main() as the callable function. Since pip is a legitimate package operation, it may not raise red flags in security scans.
The payload execu
OSV
PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions
osv·2025-03-03·CVSS 5.3
CVE-2025-1716 [MEDIUM] PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions
PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions
### CVE-2025-1889
### Summary
Picklescan fails to detect hidden pickle files embedded in PyTorch model archives due to its reliance on file extensions for detection. This allows an attacker to embed a secondary, malicious pickle file with a non-standard extension inside a model archive, which remains undetected by picklescan but is still loaded by PyTorch's torch.load() function. This can lead to arbitrary code execution when the model is loaded.
### Details
Picklescan primarily identifies pickle files by their extensions (e.g., .pkl, .pt). However, PyTorch allows specifying an alternative pickle file inside a model archive using the pickle_file parameter when calling torch.load(). This makes it possible t
OSV
Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
osv·2025-03-03·CVSS 5.3
CVE-2025-1716 [MEDIUM] Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis
### CVE-2025-1716
### Summary
An unsafe deserialization vulnerability in Python’s pickle module allows an attacker to bypass static analysis tools like Picklescan and execute arbitrary code during deserialization. This can be exploited to run pip install and fetch a malicious package, enabling remote code execution (RCE) upon package installation.
### Details
Pickle’s deserialization process allows execution of arbitrary functions via the __reduce__ method. While Picklescan is designed to detect such exploits, this attack evades detection by leveraging pip.main() as the callable function. Since pip is a legitimate package operation, it may not raise red flags in security scans.
The payload execu
OSV
CVE-2025-1716: picklescan before 0
osv·2025-02-26
CVE-2025-1716 CVE-2025-1716: picklescan before 0
picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via `pip.main()`. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-02-26
Published