Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER
CVE-2026-53875 · GHSA-97f8-7cmv-76j2 · published 2026-02-18 · updated 2026-06-18
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.55%
- Fixed in
- 1.0.3
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Craft malicious PyTorch payloads to bypass picklescan, then recall ACE/RCE.
Upgrade picklescan to 1.0.3 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| picklescan | PyPI | < 1.0.3 | 1.0.3 |
- 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.