CVE-2025-71320
Received Received - Intake
Incomplete Deny-List in Picklescan Allows Arbitrary Code Execution

Publication date: 2026-06-17

Last updated on: 2026-06-17

Assigner: VulnCheck

Description
picklescan before 0.0.33 contains an incomplete deny-list that fails to block pydoc.locate and operator.methodcaller functions, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle files using these unblocked functions to achieve arbitrary code execution when the pickle is deserialized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-17
Last Modified
2026-06-17
Generated
2026-06-17
AI Q&A
2026-06-17
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-184 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-71320 is a critical vulnerability in picklescan versions before 0.0.33 caused by an incomplete deny-list of disallowed functions.

The deny-list fails to block dangerous functions such as pydoc.locate and operator.methodcaller, which attackers can exploit.

By crafting malicious pickle files that use these unblocked functions, remote attackers can bypass security checks and achieve arbitrary code execution when the pickle is deserialized.

Impact Analysis

This vulnerability allows remote attackers to execute arbitrary code on systems that deserialize malicious pickle files using vulnerable versions of picklescan.

Successful exploitation can lead to full system compromise, including unauthorized access, data manipulation, or disruption of services.

Because the vulnerability has a high severity score (CVSS 9.3/9.8), it poses a significant security risk if not mitigated.

Detection Guidance

This vulnerability can be detected by scanning pickle files for the presence of unblocked dangerous functions such as pydoc.locate and operator.methodcaller, which are not properly denied by picklescan versions before 0.0.33.

Since picklescan is a tool designed to scan pickle files for malicious content, you can use it to detect potentially malicious pickle files. However, versions before 0.0.33 are vulnerable and may fail to detect these functions.

To detect this vulnerability on your system, you should:

  • Use an updated version of picklescan (0.0.33 or later) to scan pickle files.
  • Manually inspect pickle files for usage of pydoc.locate and operator.methodcaller functions, which can be done by analyzing the pickle file content or by deserializing in a controlled environment.
  • Example command to scan a pickle file with picklescan (assuming updated version): picklescan suspicious_file.pkl
Mitigation Strategies

The immediate and recommended mitigation step is to upgrade picklescan to version 0.0.33 or later, where the deny-list has been updated to block all dangerous functions from the pydoc and operator modules, including pydoc.locate and operator.methodcaller.

Additional mitigation steps include:

  • Avoid deserializing pickle files from untrusted or unauthenticated sources.
  • Implement additional security controls around the use of pickle deserialization, such as sandboxing or running deserialization in isolated environments.
  • Review and update any custom deny-lists or security checks to ensure they block all potentially dangerous functions, ideally using wildcards to cover all functions in risky modules.
Compliance Impact

CVE-2025-71320 allows remote attackers to achieve arbitrary code execution by bypassing security checks in picklescan due to an incomplete deny-list. This critical vulnerability can lead to unauthorized system access and data compromise.

Such unauthorized access and potential data breaches can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require strict controls to protect sensitive data and ensure system integrity.

Failure to mitigate this vulnerability could result in violations of these regulations due to exposure of personal or protected health information through exploitation of the arbitrary code execution flaw.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-71320. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart