Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist
CVE-2026-22609 · GHSA-q5qq-mvfm-j35x · published 2026-01-09 · updated 2026-01-11
- Severity
- High
- CVSS score
- 8.9
- Chance of exploitation (EPSS)
- 0.63%
- Fixed in
- 0.1.7
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
Security Bypass (Confidentiality, Integrity, Availability) An attacker can craft a malicious pickle that: 1. Imports ctypes to gain arbitrary memory access 2. Uses ctypes.pythonapi or ctypes.CDLL to execute arbitrary code 3. Passes Fickling's safety analysis as "likely safe" 4. Executes malicious code when the victim loads the pickle after trusting Fickling's verdict This undermines the core purpose of Fickling as a pickle safety scanner.
Upgrade fickling to 0.1.7 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| fickling | PyPI | <= 0.1.6 | 0.1.7 |
- CriticalLMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pylmdeploy
- CriticalLMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploylmdeploy
- CriticalSGLang: Unauthenticated RCE via --enable-custom-logit-processorsglang
- CriticalSGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socketsglang
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- HighFickling missing RCE-capable modules in UNSAFE_IMPORTSfickling
- HighFickling has `always_check_safety()` bypass: pickle.loads and _pickle.loads remain unhookedfickling
- 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
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.