CVE-2025-71371

picklescan - Remote Code Execution via code.InteractiveInterpreter Detection Bypass

Published Jun 30, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
picklescan before 0.0.29 fails to detect malicious pickle files using code.InteractiveInterpreter.runcode in reduce methods. Attackers can craft pickle payloads that bypass picklescan detection and execute arbitrary code when loaded via pickle.load().

Analysis

AI-generated

Technical impact

The vulnerability in picklescan allows an attacker to inject a specially crafted pickle payload that bypasses the tool’s attempt to detect malicious code using the InteractiveInterpreter.runcode method during reduction processing. When a vulnerable application loads a pickle file with pickle.load(), the malicious code executes, giving the attacker arbitrary code execution on the host system. This reflects a classic deserialization flaw described by CWE-502, jeopardizing confidentiality, integrity, and availability of affected installations.

Affected Systems

The affected product is picklescan developed by mmaitre314. Any instance of picklescan with a version earlier than 0.0.29 is susceptible. The vulnerability is present in the Python library that supplies the picklescan package and is commonly used by developers to scan or validate pickle objects.

Risk and Exploitability

The CVSS score of 7.6 indicates a high severity of exploitation. Because EPSS data is unavailable and the vulnerability is not listed in the CISA KEV catalog, the likelihood of a discovered exploit in the wild is uncertain, but the feasibility of exploitation is high for applications that allow external pickle input. If an attacker can supply a pickle file to a vulnerable system, they can achieve full code execution; the attack vector is therefore likely remote, via file upload or untrusted data ingestion, in applications that rely on picklescan without additional safeguards.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade picklescan to version 0.0.29 or higher, which includes a patch for the InteractiveInterpreter detection bypass.
  • If an upgrade is not immediately possible, restrict the use of pickle.load to data that has been fully validated or trusted, and consider replacing pickle with safer serialization mechanisms.
  • Configure the environment to prevent the InteractiveInterpreter or other code execution interfaces from being exposed to untrusted data, such as disabling the InteractiveInterpreter module in the application’s execution context.
  • Implement monitoring for anomalous code execution events or modifications that may indicate exploitation of deserialization vulnerabilities.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
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
Description picklescan before 0.0.29 fails to detect malicious pickle files using code.InteractiveInterpreter.runcode in reduce methods. Attackers can craft pickle payloads that bypass picklescan detection and execute arbitrary code when loaded via pickle.load().
Title picklescan - Remote Code Execution via code.InteractiveInterpreter Detection Bypass
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
Jul 1, 2026, 2:07 PM
Reserved
Jun 20, 2026, 1:01 PM
Status
Deferred
Published
Jun 30, 2026, 11:16 PM
Modified
Oct 12, 2026, 9:10 PM