PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions
CVE-2025-1889 · GHSA-769v-p64c-89pr · published 2025-03-03 · updated 2025-03-06
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.40%
- Fixed in
- 0.0.22
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Partial
- CISA SSVC
Severity: High 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 PyTorch models that remains undetected but executes when the model is loaded. Potential Exploits: This vulnerability could be exploited in supply chain attacks, backdooring pre-trained models distributed via repositories like Hugging Face or PyTorch Hub.
Upgrade picklescan to 0.0.22 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | <= 0.0.21 | 0.0.22 |
- 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.