CVE-2026-46517
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLMDeploy is a toolkit for compressing, deploying, and serving large language models. In versions 0.12.3 and prior, hardcoded "trust_remote_code=True" enables HF supply-chain RCE without user opt-in. At time of publication, there are no publicly available patches.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLMDeploy versions 0.12.3 and prior contain a hardcoded 'trust_remote_code=True' setting that enables arbitrary code execution when loading models from remote HuggingFace repositories. This supply-chain vulnerability allows attackers to achieve RCE by serving malicious models without requiring any user opt-in or explicit consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if LMDeploy is installedRun 'pip show lmdeploy' or 'pip list | grep lmdeploy' to find the installed versionAffected if LMDeploy version 0.12.3 or lower is installed and used to load HuggingFace models
-
Compare installed version to affected rangeVerify the version number from step 1 against the affected versions (0.12.3 and prior)Affected if The installed version is 0.12.3 or any version lower than 0.12.3
-
Identify LMDeploy usage with HuggingFace modelsSearch project code, scripts, or configuration files for lmdeploy imports and model loading calls, particularly involving HuggingFace model repositoriesAffected if LMDeploy is being used to load models from HuggingFace Hub or similar remote sources
-
Check trust_remote_code configurationInspect any LMDeploy configuration files, environment variables, or model loading code for explicit trust_remote_code=False settingsAffected if trust_remote_code is not explicitly set to False anywhere in the loading chain, meaning the hardcoded default applies
A user is affected if LMDeploy version 0.12.3 or prior is installed and is used to load HuggingFace models without trust_remote_code explicitly set to False.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUntil a patch is available, avoid loading models from untrusted or unverified remote sources, and explicitly set trust_remote_code=False when using HuggingFace model loading functions. Audit existing deployments for usage of LMDeploy with remote model sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data