Description
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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| mmaitre314 | picklescan | 0.0.1 – ≤ 0.0.20 | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.
GitHub 2 repositories
-
danigil/cve-2025-1716 ★ 0 · Mar 1, 2026
-
xp3s/poc_CVE-2025-1716 ★ 0 · Mar 4, 2025
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | picklescan | < 0.0.22 | 0.0.22 | GHSA-655q-fx9r-782v |
| PyPI | picklescan | < 0.0.21 | 0.0.21 | PYSEC-2025-18 |