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.
References
| Link | Resource |
|---|---|
| https://github.com/mmaitre314/picklescan/commit/78ce704227c51f070c0c5fb4b466d92c62a7aa3d | Patch |
| https://github.com/mmaitre314/picklescan/security/advisories/GHSA-655q-fx9r-782v | Exploit Vendor Advisory |
| https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-1716 | Exploit Mitigation Third Party Advisory |
Configurations
History
No history.
Information
Published : 2025-02-26 15:15
Updated : 2025-09-30 18:53
NVD link : CVE-2025-1716
Mitre link : CVE-2025-1716
CVE.ORG link : CVE-2025-1716
JSON object : View
Products Affected
mmaitre314
- picklescan
CWE
CWE-184
Incomplete List of Disallowed Inputs
