CVE-2025-1716
Mmaitre314 Picklescan vulnerability
- Published26 Feb 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-1716 being actively exploited?
CVE-2025-1716 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.71%.
How severe is CVE-2025-1716?
CVE-2025-1716 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.71% probability of exploitation.
Which products are affected by CVE-2025-1716?
Affected products include Mmaitre314 Picklescan.
How do I fix CVE-2025-1716?
Upgrade affected software to a fixed version, for example Mmaitre314 Picklescan 0.0.22 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-1716 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.