UTC
Critical

LMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.py

CVE-2025-66455 · GHSA-2vh9-42vm-xmv2 · published 2026-09-18 · updated 2026-09-21

Severity
Critical
CVSS score
9.8
Chance of exploitation (EPSS)
1.3%
Fixed in
0.16.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

Successful exploitation allows arbitrary code execution as the LMDeploy serving process. This can expose model weights, prompts, credentials, attached storage, cluster-network services, and host or GPU resources. An attacker may also modify or terminate the serving process.

What to do

Upgrade lmdeploy to 0.16.0 or later.

The issue was fixed by replacing the pickle-based ZeroMQ protocol with JSON serialization: send_pyobj() was replaced with send_json(). recv_pyobj() was replaced with recv_json(). Received objects are validated using the DistServeCacheFreeRequest Pydantic schema before use. Invalid or off-schema messages are rejected without terminating the receive loop. Fix commit: https://github.com/InternLM/lmdeploy/commit/f05b4ad8bf2e2d84101a1d63b3c44fadd99223b2 The fix was released in LMDeploy 0.16.0.

If you cannot upgrade yet

Users who cannot upgrade immediately should: Prevent untrusted clients from reaching /distserve/* endpoints. Restrict the DistServe HTTP and ZeroMQ control planes to trusted cluster networks. Configure API-key authentication. Block arbitrary outbound ZeroMQ connections from serving nodes. These measures reduce exposure but do not make pickle deserialization safe. Upgrading to LMDeploy 0.16.0 or later is recommended.

Affected
PackageRegistryAffectedFixed in
lmdeployPyPI>= 0.9.2, < 0.16.00.16.0

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].