Fickling has Code Injection vulnerability via pty.spawn()
CVE-2025-67748 · GHSA-r7v6-mfhq-g3m2 · published 2025-12-15 · updated 2026-06-05
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.29%
- Fixed in
- 0.1.6
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
This allows an attacker to craft a malicious pickle file that can bypass fickling since it relies on the "unused variable" heuristic to flag pickle files as unsafe. A user who deserializes such a file, believing it to be safe, would inadvertently execute arbitrary code on their system. This impacts any user or system that uses Fickling to vet pickle files for security issues.
Upgrade fickling to 0.1.6 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| fickling | PyPI | < 0.1.6 | 0.1.6 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- 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.