Picklescan Bypasses Unsafe Globals Check using pty.spawn
CVE-2025-71322 · GHSA-hgrh-qx5j-jfwx · published 2025-12-29 · updated 2026-06-18
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.38%
- Fixed in
- 0.0.33
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
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 and bypass the PickleScan check by using the pty.spawn function. This could lead to arbitrary code execution on the user's system when these malicious files are processed or loaded.
Upgrade picklescan to 0.0.33 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | < 0.0.33 | 0.0.33 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalPickleScan's profile.run blocklist mismatch allows exec() bypasspicklescan
- CriticalPickleScan has multiple stdlib modules with direct RCE not in blocklistpicklescan
- CriticalPickleScan's pkgutil.resolve_name has a universal blocklist bypasspicklescan
- CriticalPicklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Importspicklescan
- CriticalPicklescan Bypass is Possible via File Extension Mismatchpicklescan
- CriticalPicklescan: ZIP archive scan bypass is possible through non-exhaustive Cyclic Redundancy Checkpicklescan
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.