Fickling has `always_check_safety()` bypass: pickle.loads and _pickle.loads remain unhooked
GHSA-wccx-j62j-r448 · published 2026-03-04
- Severity
- High
- CVSS score
- 8.9
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.1.9
High-confidence runtime protection bypass for applications that trust alwayschecksafety() as global guard.
Upgrade fickling to 0.1.9 or later.
pickle.loads, pickle.loads, and pickle.load all raise UnsafeFileError sink not called in any path Regression tests added locally: testrunhookblockspickle_loads
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| fickling | PyPI | <= 0.1.8 | 0.1.9 |
- 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
- HighFickling missing RCE-capable modules in UNSAFE_IMPORTSfickling
- HighFickling: OBJ opcode call invisibility bypasses all safety checksfickling
- HighFickling vulnerable to use of ctypes and pydoc gadget chain to bypass detectionfickling
- HighFickling vulnerable to detection bypass due to "builtins" blindnessfickling
- HighFickling Blocklist Bypass: cProfile.run()fickling
- HighFickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklistfickling
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.