CVE-2025-71344: Picklescan is missing detection when calling built-in python ensurepip._run_pip
Affects picklescanSource GCVE Database
Not known to be exploited : upgrade to 0.0.30 soon.
Data as of 25 Oct 2026, 19:02 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.0.30
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade picklescan to 0.0.30.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIpicklescan | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid relying solely on Picklescan versions prior to 0.0.30 for detecting malicious pickle files involving ensurepip._run_pip. If you cannot patch yet, consider additional validation or sandboxing when loading pickle files from untrusted sources.
Description
Picklescan versions prior to 0.0.30 fail to detect malicious pickle files that exploit the built-in Python function ensurepip._run_pip. This allows attackers to embed and execute arbitrary code when such pickle files are loaded, bypassing Picklescan's detection. The vulnerability impacts users relying on Picklescan to validate pickle files, including those embedded in PyTorch models. This can facilitate supply chain attacks by distributing infected pickle files across machine learning models, APIs, or saved Python objects.
References
- github.com/mmaitre314/picklescan/security/advisories/GHSA-xp4f-hrf8-rxw7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-71344 (opens in a new tab)
- github.com/mmaitre314/picklescan/commit/1931c2d04eaca8d20597705ff39cab78ba364e4b (opens in a new tab)
- github.com/advisories/GHSA-xp4f-hrf8-rxw7 (opens in a new tab)
- github.com/mmaitre314/picklescan (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/picklescan/PYSEC-2026-1792.yaml (opens in a new tab)
- pypi.org/project/picklescan (opens in a new tab)
- vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-undetected-ensurepip-run-pip-function (opens in a new tab)