CVE-2026-46432

LMDeploy: Arbitrary code execution via hardcoded trustremotecode=True in lmdeploy model initialization

An attacker who can control the model path used by an lmdeploy deployment can execute arbitrary Python code during model initialization.

The attacker may be able to:

• Read files accessible to the lmdeploy process.
• Access environment variables, model provider credentials, HuggingFace tokens, cloud credentials, and API keys.
• Modify model-serving behavior or tamper with responses.
• Execute arbitrary operating-system commands.
• Access request data or internal service credentials available to the serving process.
• Cause denial of service by crashing or destabilizing the serving daemon.
• Pivot to internal services reachable from the lmdeploy host or container.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-46432 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.13.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-46432? CVE-2026-46432 is a high-severity code injection vulnerability in lmdeploy (pip), affecting versions < 0.13.0. It is fixed in 0.13.0. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-46432? CVE-2026-46432 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of lmdeploy are affected by CVE-2026-46432? lmdeploy (pip) versions < 0.13.0 is affected.
4. Is there a fix for CVE-2026-46432? Yes. CVE-2026-46432 is fixed in 0.13.0. Upgrade to this version or later.
5. Is CVE-2026-46432 exploitable, and should I be worried? Whether CVE-2026-46432 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-46432 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-46432? Upgrade lmdeploy to 0.13.0 or later.