Picklescan is missing detection when calling built-in python ensurepip._run_pip (CVE-2025-71344)
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.
AI Analysis
Technical Summary
Picklescan, a library used to detect malicious pickle files, does not detect payloads that use the built-in Python function ensurepip._run_pip to execute remote pickle files. An attacker crafts a malicious pickle payload that calls ensurepip._run_pip in its __reduce__ method. When Picklescan fails to detect this as dangerous, the victim may load the pickle file using pickle.load(), resulting in remote code execution. This vulnerability affects Picklescan versions before 0.0.30 and is tracked as CVE-2025-71344.
Potential Impact
Attackers can embed malicious code in pickle files that evade detection by Picklescan and execute upon loading. This can lead to remote code execution in environments that trust Picklescan's validation, including machine learning workflows and APIs that load pickle files. The vulnerability enables supply chain attacks by distributing infected pickle files within PyTorch models or other Python objects. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid relying solely on Picklescan versions prior to 0.0.30 for detecting malicious pickle files involving ensurepip._run_pip. Until an official fix is available, consider additional validation or sandboxing when loading pickle files from untrusted sources.
Picklescan is missing detection when calling built-in python ensurepip._run_pip (CVE-2025-71344)
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.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Picklescan, a library used to detect malicious pickle files, does not detect payloads that use the built-in Python function ensurepip._run_pip to execute remote pickle files. An attacker crafts a malicious pickle payload that calls ensurepip._run_pip in its __reduce__ method. When Picklescan fails to detect this as dangerous, the victim may load the pickle file using pickle.load(), resulting in remote code execution. This vulnerability affects Picklescan versions before 0.0.30 and is tracked as CVE-2025-71344.
Potential Impact
Attackers can embed malicious code in pickle files that evade detection by Picklescan and execute upon loading. This can lead to remote code execution in environments that trust Picklescan's validation, including machine learning workflows and APIs that load pickle files. The vulnerability enables supply chain attacks by distributing infected pickle files within PyTorch models or other Python objects. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid relying solely on Picklescan versions prior to 0.0.30 for detecting malicious pickle files involving ensurepip._run_pip. Until an official fix is available, consider additional validation or sandboxing when loading pickle files from untrusted sources.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xp4f-hrf8-rxw7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-71344"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a600ac79c2644c7f8fe3a8e
Added to database: 07/22/2026, 00:11:51 UTC
Last enriched: 07/22/2026, 00:56:32 UTC
Last updated: 07/22/2026, 01:53:58 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.