lmdeploy vulnerable to Arbitrary Code Execution via Insecure Deserialization in torch.load()
CVE-2025-67729 · GHSA-9pf3-7rrr-x5jh · published 2025-12-26 · updated 2025-12-27
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.51%
- Fixed in
- 0.11.1
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
An insecure deserialization vulnerability exists in lmdeploy where torch.load() is called without the weightsonly=True parameter when loading model checkpoint files. This allows an attacker to execute arbitrary code on the victim's machine when they load a malicious .bin or .pt model file. CWE:** CWE-502 - Deserialization of Untrusted Data ---
Upgrade lmdeploy to 0.11.1 or later.
Add weights_only=True to all torch.load() calls:
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| lmdeploy | PyPI | <= 0.11 | 0.11.1 |
- 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
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
- 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
- HighLMDeploy has an SSRF bypasslmdeploy
- HighLMDeploy vulnerable to arbitrary code execution via eval() of untrusted quant_dtype in model config loadinglmdeploy
- Highlmdeploy: Hardcoded trust_remote_code=True is an implicit unsafe remote-code load path with no user opt-outlmdeploy
- HighLMDeploy: Arbitrary code execution via hardcoded trust_remote_code=True in lmdeploy model initializationlmdeploy
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.