Picklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Imports
Summary
The vulnerability allows malicious actors to bypass PickleScan's unsafe globals check, leading to potential arbitrary code execution. The issue stems from PickleScan's strict check for full module names against its list of unsafe globals. By using subclasses of dangerous imports instead of the exact module names, attackers can circumvent the check and inject malicious payloads.
PoC
- Download a model that uses the
asynciopackage:
wget https://huggingface.co/iluem/linux_pkl/resolve/main/asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl
- Check with PickleScan:
picklescan -p asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl -g
Expected Result:
PickleScan should identify all asyncio import as dangerous and flag the pickle file as malicious as asyncio is in _unsafe_globals dictionary.
Actual Result:
PickleScan marked the import as Suspicious, failing to identify it as a dangerous import.
Impact
Severity: High Affected Users: Any organization, like HuggingFace, or individual using PickleScan to analyze PyTorch models or other files distributed as ZIP archives for malicious pickle content. Impact Details: Attackers can craft malicious PyTorch models containing embedded pickle payloads, package them into ZIP archives, and bypass the PickleScan check by using subclasses of dangerous imports. This could lead to arbitrary code execution on the user's system when these malicious files are processed or loaded.
Recommendations:
unsafe_filter = _unsafe_globals.get(g.module)
by:
matched_key = None
if imported_global.module:
for key_in_globals in unsafe_globals.keys():
# Check if imported_global.module starts with the key_in_globals AND
# (it's the first match OR this key is more specific than the previous match)
# AND imported_global.module is exactly the key or imported_global.module is key + '.' + something
if imported_global.module.startswith(key_in_globals):
if (imported_global.module == key_in_globals or # Exact match
(len(imported_global.module) > len(key_in_globals) and imported_global.module[len(key_in_globals)] == '.')): # Submodule match
if matched_key is None or len(key_in_globals) > len(matched_key):
matched_key = key_in_globals
if matched_key:
unsafe_filter = unsafe_globals[matched_key]
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | picklescan | < 0.0.31 | 0.0.31 |
References
- https://github.com/mmaitre314/picklescan/blob/2a8383cfeb4158567f9770d86597300c9e508d0f/src/picklescan/scanner.py#L309
- https://huggingface.co/iluem/linux_pkl/resolve/main/asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl
- https://github.com/mmaitre314/picklescan/security/advisories/GHSA-f7qq-56ww-84cr
- https://nvd.nist.gov/vuln/detail/CVE-2025-10157
- https://github.com/mmaitre314/picklescan/pull/50
- https://github.com/mmaitre314/picklescan/commit/28a7b4ef753466572bda3313737116eeb9b4e5c5
- https://github.com/mmaitre314/picklescan
- https://github.com/pypa/advisory-database/tree/main/vulns/picklescan/PYSEC-2025-153.yaml
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L- Weakness (CWE)
CWE-693- Platform
- Python (PyPI)
- Package
picklescan- Disclosed
- 10.09.2025
- Updated
- 11.10.2026 12:19
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2025-153 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-f7qq-56ww-84cr - CC BY 4.0
Vulnerability history: picklescan
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 58
- First → latest
- 02.2025 03.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 7
- High 25
- Medium 26
Disclosures per year
- 2025: 51
- 2026: 7
-
Picklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Imports this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.