https://feed.craftedsignal.io/products/picklescan--0.0.29/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 04 Jul 2026 02:24:27 +0000https://feed.craftedsignal.io/briefs/2026-07-cve-2025-71360-picklescan-rce/Sat, 04 Jul 2026 02:24:27 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-cve-2025-71360-picklescan-rce/A high-severity deserialization of untrusted data vulnerability (CVE-2025-71360) in picklescan versions before 0.0.29 allows attackers to embed undetected remote command execution code within malicious pickle files, leading to arbitrary code execution when loaded by victims.CVE-2025-71360 describes a critical deserialization vulnerability impacting picklescan versions prior to 0.0.29, a Python library designed to detect malicious code within Python pickle files. Specifically, the flaw lies in picklescan's failure to detect malicious code embedded using the idlelib.calltip.get_entity function within pickle reduce methods. This oversight allows attackers to craft specially designed pickle files containing arbitrary Python code that bypasses picklescan's security checks. When a victim subsequently loads such a malicious pickle file, the embedded code is executed, enabling remote command execution (RCE) on the affected system. This vulnerability poses a significant risk to applications that process or scan untrusted pickle files, as it effectively nullifies the security benefits picklescan is intended to provide.

Attack Chain

1. An attacker crafts a malicious Python pickle file containing arbitrary code, leveraging the idlelib.calltip.get_entity function within the pickle's __reduce__ method to embed their payload.
2. The attacker distributes this specially crafted pickle file to a target system, potentially through email attachments, untrusted file downloads, or as part of a compromised data exchange.
3. A victim receives and attempts to process or scan the untrusted pickle file using an affected version of the picklescan library (prior to 0.0.29).
4. The picklescan library, when performing its security checks, fails to correctly identify and flag the malicious code embedded via idlelib.calltip.get_entity.
5. The malicious pickle file is then loaded or deserialized by a Python application or script on the victim's system.
6. During the deserialization process, the embedded code within the pickle file executes, leading to arbitrary remote command execution on the victim's system, granting the attacker control.

Impact

Successful exploitation of CVE-2025-71360 leads to arbitrary remote code execution on the victim's system. This can result in complete system compromise, allowing attackers to install malware, exfiltrate sensitive data, establish persistence, or pivot to other systems within the network. Organizations relying on picklescan for validating untrusted data could be unknowingly processing malicious content, leading to widespread compromise. The direct impact is the subversion of a security control, enabling attackers to bypass detection and execute their payloads.

Recommendation

• Immediately update picklescan to version 0.0.29 or newer to remediate CVE-2025-71360.
• Implement strict controls around the handling and loading of Python pickle files, treating all external or untrusted pickle files as potentially malicious.
• Educate users and developers on the dangers of deserializing untrusted data and the importance of using secure deserialization alternatives or strict validation.
• Consider deploying application-level sandboxing or isolation for processes that handle pickle file deserialization to limit the impact of potential RCE.

]]>highadvisorydeserializationrcevulnerabilitypythonhttps://feed.craftedsignal.io/briefs/2026-07-cve-2025-71359-picklescan-rce/Sat, 04 Jul 2026 02:23:45 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-cve-2025-71359-picklescan-rce/Picklescan versions prior to 0.0.29 are vulnerable to remote code execution (CVE-2025-71359) due to a failure in detecting malicious Python pickle payloads that utilize `lib2to3.pgen2.grammar.Grammar.loads`, allowing attackers to craft files that evade detection and execute arbitrary code during deserialization.This brief addresses CVE-2025-71359, a high-severity vulnerability impacting picklescan versions before 0.0.29. The picklescan library, designed to detect malicious Python pickle payloads, fails to identify specific evasion techniques. Specifically, attackers can craft pickle files that embed dangerous code by leveraging lib2to3.pgen2.grammar.Grammar.loads within the __reduce__ method. These specially crafted payloads bypass picklescan's scrutiny. When an application subsequently deserializes such an untrusted pickle file using Python's pickle.load(), the embedded malicious code executes on the host system. This remote code execution (RCE) can grant attackers significant control over the compromised environment, allowing for data exfiltration, system modification, or further network penetration. The vulnerability highlights the inherent risks of deserializing untrusted data and the need for robust validation mechanisms.

Attack Chain

1. Craft Malicious Pickle Payload: An attacker crafts a Python pickle file (.pkl) embedding arbitrary code, specifically utilizing lib2to3.pgen2.grammar.Grammar.loads within the __reduce__ method to achieve RCE.
2. Evade Security Scanner: The crafted malicious payload is designed to exploit the flaw in picklescan versions prior to 0.0.29, allowing it to bypass its detection mechanisms.
3. Delivery of Malicious File: The attacker delivers the malicious pickle file to a target system. This could occur via various vectors, such as uploading to a vulnerable web application, attaching it to a phishing email, or injecting it into a compromised software supply chain.
4. Target Application Processes Pickle File: A vulnerable application on the target system receives and attempts to deserialize the seemingly benign (undetected by picklescan) malicious pickle file using Python's pickle.load() function.
5. Deserialization and Code Execution: During the deserialization process, the __reduce__ method within the pickle object is invoked, and the embedded Grammar.loads executes the attacker's arbitrary code.
6. Remote Code Execution (RCE): The attacker's code runs with the privileges of the vulnerable application, leading to remote code execution on the target system.

Impact

Successful exploitation of CVE-2025-71359 results in remote code execution (RCE) on the host system where the vulnerable picklescan library is used to validate and subsequently deserialize malicious pickle files. This level of access allows attackers to take complete control of the affected application and potentially the underlying server. Consequences can include unauthorized data access, modification, or deletion, installation of malware (e.g., ransomware, backdoors), lateral movement within the network, and complete system compromise. The severity of the impact depends on the privileges of the compromised application and the data it processes.

Recommendation

• Immediately update picklescan to version 0.0.29 or newer to remediate CVE-2025-71359.
• Implement strict input validation and sanitization for all incoming pickle files, regardless of picklescan usage.
• Adopt secure deserialization practices by never deserializing untrusted data. If deserialization is unavoidable, implement restricted unpickling environments, such as those that limit available classes and functions during pickle.load().

]]>highadvisoryremote-code-executiondeserializationpythonvulnerabilitysupply-chain