Picklescan is missing detection when calling built-in python ensurepip._run_pip
CVE-2025-71344 · GHSA-xp4f-hrf8-rxw7 · published 2025-08-26 · updated 2026-07-21
- Severity
- High
- CVSS score
- 8.1
- Chance of exploitation (EPSS)
- 0.47%
- Fixed in
- 0.0.30
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.
Upgrade picklescan to 0.0.30 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | < 0.0.30 | 0.0.30 |
- CriticalLMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pylmdeploy
- CriticalLMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploylmdeploy
- CriticalSGLang: Unauthenticated RCE via --enable-custom-logit-processorsglang
- CriticalSGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socketsglang
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- CriticalPickleScan's profile.run blocklist mismatch allows exec() bypasspicklescan
- CriticalPickleScan has multiple stdlib modules with direct RCE not in blocklistpicklescan
- CriticalPickleScan's pkgutil.resolve_name has a universal blocklist bypasspicklescan
- CriticalPicklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Importspicklescan
- CriticalPicklescan Bypass is Possible via File Extension Mismatchpicklescan
- CriticalPicklescan: ZIP archive scan bypass is possible through non-exhaustive Cyclic Redundancy Checkpicklescan
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.