CVE-2025-10157 — picklescan
Fix: mmaitre314/picklescan#50CVE-2025-10157 is a CWE-693 vulnerability in picklescan. A fix is available for picklescan — see the affected versions and patch details below.
PickleScan Bypasses Unsafe Globals Check Using Submodule Imports
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10157.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
picklescanReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | picklescan | all versions | 0.0.31pip install --upgrade 'picklescan==0.0.31' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for picklescan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update picklescan to 0.0.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10157 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-10157 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-10157. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-10157 in your dependencies?
O3 Security finds CVE-2025-10157 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.