CVE-2025-1716: picklescan - Security scanning bypass via 'pip main'
mmaitre314 · picklescan
Fixed in 0.0.21 · Affected: mmaitre314 picklescan before 0.0.21 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 77% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- mmaitre314 · picklescanfrom 0.0.1 up to and including 0.0.20
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- mmaitre314
- Published
- February 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-1716 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.