UTC
Medium

Fickling has safety check bypass via REDUCE+BUILD opcode sequence

GHSA-mhc9-48gj-9gp3 · published 2026-02-25

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
No CVE
Fixed in
0.1.8
What it is

An attacker can distribute a malicious pickle file (e.g., a backdoored ML model) that passes all fickling safety checks. Demonstrated impacts include: Backdoor network listener: opens a port on all interfaces, accepting connections from the network. The TCPServer constructor calls serverbind() and serveractivate(), so the port is open immediately after pickle.loads() returns. Process persistence: signal.signal(SIGTERM, SIGIGN) makes the process ignore SIGTERM. In Kubernetes/Docker/ECS, the orchestrator cannot gracefully shut down the process — the backdoor stays alive for 30+ seconds per restart attempt.

What to do

Upgrade fickling to 0.1.8 or later.

Restrict likelysafeimports to a curated allowlist of known-safe modules instead of trusting all stdlib modules. Additionally, either remove the OvertlyBadEvals exemption for likelysafeimports or expand the UNSAFE_IMPORTS blocklist to cover network/file/compilation modules.

Affected
PackageRegistryAffectedFixed in
ficklingPyPI<= 0.1.70.1.8

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].