Mmaitre314 picklescan
picklescan - Security scanning bypass via 'pip main'
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 versions and mitigation
From the CVE record, GitHub Security Advisories and the vendor's references.Affected
- >= 0.0.1, <= 0.0.20
Mitigation
Upgrade picklescan to 0.0.22 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 6.4 days after publication; not in CISA KEV. First PoC: xp3s/poc_CVE-2025-1716 (created 4 Mar 2025, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs · 2 pending
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| xp3s/poc_CVE-2025-1716 | 4 Mar 2025 +6.4 d | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Pending 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| N3mes1s/pruva-sandbox | 6 Jan 2026 +314 d | 8 | Pending · listed by PoC Index; via PoC Index |
| danigil/cve-2025-1716 | 1 Mar 2026 +1.0 y | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.