Code Injection in lmdeploy (CVE-2026-46432)
Summary
Code injection in lmdeploy (CVE-2026-46432). Successful exploitation can lead to full system takeover. Exploitable via model_path. Mitigation: upgrade to 0.13.0 or later.
Original description
The description as published by the source.
LMDeploy is a toolkit for compressing, deploying, and serving large language models. In versions 0.12.3 and prior, LMDeploy is vulnerable to arbitrary code execution through hardcoded "trust_remote_code=True" in multiple HuggingFace model-loading call sites. At time of publication, there are no publicly available patches.
Source: GitHub Security Advisories (Global) 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-2026-46432 has been found in lmdeploy.
Attackers can target a specific entry point like model_path over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade lmdeploy to 0.13.0 or later.
If unsure, ask your IT team or search "lmdeploy CVE-2026-46432" on the vendor's site.
CVE-2026-46432 (lmdeploy) — CWE-94 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: model_path / main
Patched: 0.13.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.
Arbitrary code execution (CWE-94) exists in lmdeploy. Attackers reach the vulnerable code path via model_path.
Check the vendor advisory for the affected versions of lmdeploy. Attack surface: model_path / main.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.13.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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade lmdeploy to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com