CVE-2025-71344

picklescan - Arbitrary Code Execution via Undetected ensurepip._run_pip Function

Published Jun 22, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
picklescan before 0.0.30 (affected versions 0.0.26 and earlier) fails to detect the ensurepip._run_pip built-in function when scanning pickle files, allowing attackers to execute arbitrary code. Malicious pickle files embedding ensurepip._run_pip calls in __reduce__ methods bypass picklescan detection and achieve remote code execution upon pickle.load() invocation.

Analysis

AI-generated

Technical impact

picklescan before 0.0.30 fails to detect calls to the standard library's ensurepip._run_pip function when scanning pickle data, allowing an attacker to embed such calls in a malicious pickle's __reduce__ method. Loading the pickle file with pickle.load() will trigger the hidden function and execute arbitrary code in the process. The weakness is a classic deserialization flaw (CWE-502) that results in full code execution.

Affected Systems

The vulnerability affects the picklescan utility provided by mmaitre314. Versions 0.0.26 and earlier are impacted; any deployment of these releases is susceptible to exploitation.

Risk and Exploitability

The assessed CVSS score of 7.6 indicates high potential impact. EPSS data is not available, and the issue is not listed in the CISA KEV catalog, suggesting that public exploits may not yet exist but the risk remains significant. Based on the description, the likely attack vector is an attacker who can supply a crafted pickle file to a system that loads such data using picklescan; upon deserialization, the system will execute the injected code.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade picklescan to version 0.0.30 or later, which removes the instrumentation that fails to detect ensurepip._run_pip calls.
  • Use controlled and trusted sources for pickle files, and avoid loading untrusted data with pickle.load().
  • When deserialization of external data is unavoidable, run the process in a sandbox or with reduced privileges to contain any potential code execution.
  • Consider implementing checksum verification or alternative, safer serialization formats to prevent malicious pickle files from being processed.

Generated by OpenCVE AI on June 22, 2026 at 23:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-xp4f-hrf8-rxw7 Picklescan is missing detection when calling built-in python ensurepip._run_pip
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Picklescan
Picklescan picklescan
Vendors & Products Picklescan
Picklescan picklescan
Type Values Removed Values Added
Description picklescan before 0.0.30 (affected versions 0.0.26 and earlier) fails to detect the ensurepip._run_pip built-in function when scanning pickle files, allowing attackers to execute arbitrary code. Malicious pickle files embedding ensurepip._run_pip calls in __reduce__ methods bypass picklescan detection and achieve remote code execution upon pickle.load() invocation.
Title picklescan - Arbitrary Code Execution via Undetected ensurepip._run_pip Function
First Time appeared Mmaitre314
Mmaitre314 picklescan
Weaknesses CWE-502
CPEs cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*
Vendors & Products Mmaitre314
Mmaitre314 picklescan
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jun 23, 2026, 6:24 PM
Reserved
Jun 20, 2026, 12:48 PM
Status
Deferred
Published
Jun 22, 2026, 10:16 PM
Modified
Oct 12, 2026, 10:10 PM