Unsafe Deserialization in lmdeploy (CVE-2025-66455)
Summary
Vulnerability in lmdeploy (CVE-2025-66455). Successful exploitation can lead to full system takeover. Exploitable via POST /distserve/p2p_connect. Mitigation: upgrade to 0.16.0 or later.
Original description
The description as published by the source.
Summary
LMDeploy's PyTorch DistServe/PD-disaggregation control plane used
recv_pyobj() to deserialize messages received through a ZeroMQ PULL
socket. PyZMQ implements recv_pyobj() using Python pickle
deserialization, which can execute arbitrary code while reconstructing
an object.
The peer address used by the receiver was supplied through the
POST /distserve/p2p_connect HTTP endpoint. An attacker who could reach
an affected DistServe API server could cause the server to connect to an
attacker-controlled ZeroMQ endpoint and deserialize a crafted pickle
payload.
API-key authentication is not enabled unless the operator explicitly
configures it. As a result, affected DistServe deployments without API
keys allowed unauthenticated remote code execution with the privileges
of the LMDeploy serving process.
This issue affects the PyTorch backend when PD-disaggregation/DistServe
is enabled. Ordinary deployments that do not use the affected
disaggregated-serving path do not expose this data flow.
Affected components
- HTTP entry point:
lmdeploy/serve/openai/endpoints/distserve.py,
POST /distserve/p2p_connect - Attacker-controlled peer address:
DistServeConnectionRequest.remote_engine_endpoint_info.zmq_address - Vulnerable receiver:
lmdeploy/pytorch/disagg/conn/engine_conn.py,
EngineP2PConnection.handle_zmq_recv() - Unsafe operation:
recv_pyobj(), which performs pickle deserialization
Vulnerable data flow
- A caller submits a DistServe P2P c…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-66455 has been found in lmdeploy.
Attackers can target a specific entry point like POST /distserve/p2p_connect over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade lmdeploy to 0.16.0 or later.
If unsure, ask your IT team or search "lmdeploy CVE-2025-66455" on the vendor's site.
CVE-2025-66455 (lmdeploy) — CWE-502 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /distserve/p2p_connect / b0b705f7 / DistServeCacheFreeRequest
Patched: 0.16.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in lmdeploy. Attackers reach the vulnerable code path via POST /distserve/p2p_connect without authentication.
Check the vendor advisory for the affected versions of lmdeploy. Attack surface: POST /distserve/p2p_connect / b0b705f7 / DistServeCacheFreeRequest.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 0.16.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /distserve/p2p_connect requests with malformed payloads or SQL meta-characters. Run grep -r 'lmdeploy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'lmdeploy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lmdeployを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /distserve/p2p_connect' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /distserve/p2p_connectへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade lmdeploy to 0.16.0ステージング環境で 0.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /distserve/p2p_connect on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com