PickleScan has multiple stdlib modules with direct RCE not in blocklist
CVE-2026-56315 · GHSA-g38g-8gr9-h9xp · published 2026-03-03 · updated 2026-09-25
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 1.1%
- Fixed in
- 1.0.4
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
Any system using picklescan for pickle safety validation is vulnerable. This includes: HuggingFace Hub — uses picklescan server-side to scan uploaded model files ML pipelines — any CI/CD or loading pipeline using picklescan Model registries — any registry relying on picklescan for safety checks An attacker can upload a malicious model file to HuggingFace Hub that passes all picklescan checks and executes arbitrary code when loaded by a user.
Upgrade picklescan to 1.0.4 or later.
Add to unsafeglobals in picklescan: Architectural recommendation: The blocklist approach is fundamentally flawed — new RCE-capable stdlib functions can be discovered faster than they are blocked. Consider: 1. Switching to an allowlist (default-deny) for permitted globals 2. Treating ALL unknown globals as dangerous by default (currently marked "Suspicious" but not counted as issues)
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | < 1.0.4 | 1.0.4 |
- 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'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
- HighPicklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBERpicklescan
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.