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.
{
"cna_assigner": "Sonatype",
"cwe_ids": [
"CWE-184"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1716.json"
}{
"cpe": "cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*",
"extracted_events": [
{
"introduced": "0"
},
{
"fixed": "0.0.22"
}
],
"source": [
"CPE_RANGE",
"REFERENCES"
]
}