Quick answers
- Is CVE-2026-46517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46517 being exploited in the wild.
- How severe is CVE-2026-46517?
- High severity, with a CVSS score of 7.8, published 10 June 2026.
- Which products and versions are affected?
- lmdeploy (PyPI) <= 0.12.3, ECOSYSTEM:introduced=0,fixed=0.13.0, ECOSYSTEM:introduced=0,last_affected=0.12.3.
- Is there a fix for CVE-2026-46517?
- Yes. lmdeploy (PyPI): upgrade to 0.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46517 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-46517?
- Check whether you run lmdeploy (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- lmdeploy (PyPI): upgrade to 0.13.0 or later
pip install "lmdeploy>=0.13.0"
Technical details
LMDeploy (versions <= 0.12.3) hardcodes the 'trust_remote_code=True' parameter in several critical model-loading components, including 'archs.py' and 'calibrate.py'. This bypasses the default-secure stance of the Hugging Face Transformers library, which requires explicit user consent to execute remote code. When a user provides a model path or repository ID, LMDeploy calls 'AutoConfig.from_pretrained' with this hardcoded flag, causing the library to download and execute arbitrary Python code defined in the repository's 'configuration_*.py' file via 'importlib'. An attacker can achieve full code execution in the context of the LMDeploy process user by tricking a user into loading a malicious model. As of the advisory date, no official patch is available.
Affected products
- InternLM LMDeploy <= 0.12.3
Identifiers
- CVE-2026-46517
- GHSA-9xq9-36w5-q796
- PYSEC-2026-2608
Timeline
- 2026-05-02: other: Vulnerability identified and reframed by researchers
- 2026-05-15: advisory: GitHub Security Advisory published
- 2026-06-10: disclosed: CVE published to NVD