Home › Vulnerabilities

InternLM LMDeploy Flaw CVE-2026-119706: Update Now

Published November 1, 2026 · Last updated November 1, 2026

CVE Critical Patch

The short version: CVE-2026-119706 is a critical-severity security flaw in InternLM LMDeploy. The National Vulnerability Database (NVD) published it on October 30, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on November 1, 2026, CISA had not added CVE-2026-119706 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-119706

The record was filed by vulncheck.com. In its own words: "InternLM LMDeploy 0.9.0 through 0.18.0 contains an unauthenticated remote code execution vulnerability that allows remote attackers to run OS commands by sending pickled data to the /update_weights endpoint. Attackers can submit a base64-encoded crafted pickle in serialized_named_tensors, which ForkingPickler.loads deserializes without validation, executing commands as the api_server process."

Why LMDeploy admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-119706 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping LMDeploy running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on vulncheck.com gives it 9.3 (Critical, CVSS 4.0).

Affected LMDeploy releases

According to the record, these releases are vulnerable:

  • 0.9.0 through 0.18.0

The type of bug behind CVE-2026-119706

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-502, Deserialization of Untrusted Data. MITRE describes this class of bug as follows: "The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid."

Vendor remediation for CVE-2026-119706

The vendor advisory remediation for operators of LMDeploy, quoted for this page, is: "No fixed LMDeploy release was out when FraudMeNot checked on November 1, 2026. The newest published release, v0.18.0 from September 28, is still affected, and the proposed fix (pull request 4964, titled Reject pickle on HTTP /update_weights, tied to issue 4698) had not yet been merged. Every LMDeploy version from 0.9.0 through 0.18.0 accepts a base64-encoded serialized_named_tensors field on the /update_weights route and unpickles it, so whoever can reach the api_server port can make it run shell commands. Until a patched version ships, keep the api_server bound to localhost or a private subnet, put an authenticating reverse proxy in front of it, and have that proxy refuse any request to /update_weights. Check cloud security groups and Kubernetes Services for LMDeploy ports open to 0.0.0.0, and look at the server process for unexpected child processes. Machine learning and platform teams that self-host large language models with LMDeploy should act now."

What to do about it

  • Update now: No fixed LMDeploy release was out when FraudMeNot checked on November 1, 2026. The newest published release, v0.18.0 from September 28, is still affected, and the proposed fix (pull request 4964, titled Reject pickle on HTTP /update_weights, tied to issue 4698) had not yet been merged. Every LMDeploy version from 0.9.0 through 0.18.0 accepts a base64-encoded serialized_named_tensors field on the /update_weights route and unpickles it, so whoever can reach the api_server port can make it run shell commands. Until a patched version ships, keep the api_server bound to localhost or a private subnet, put an authenticating reverse proxy in front of it, and have that proxy refuse any request to /update_weights. Check cloud security groups and Kubernetes Services for LMDeploy ports open to 0.0.0.0, and look at the server process for unexpected child processes. Machine learning and platform teams that self-host large language models with LMDeploy should act now.
  • Who should act: IT teams, managed service providers, and developers who run or ship LMDeploy. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from InternLM (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 30, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-119706. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-119706 record details from CISA and NVD

  • Attack complexity for CVE-2026-119706: low
  • CVE-2026-119706 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-119706: exploitability 3.9, impact 5.9.
  • Who mapped the weakness type: the address listed on vulncheck.com (Primary)
  • References in the NVD record: 7.
  • CISA SSVC decision points for CVE-2026-119706 (from NVD): exploitation=poc; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • October 30, 2026: NVD publishes CVE-2026-119706.
  • November 1, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-119706 is not listed.
  • October 30, 2026: most recent NVD update (record status: Deferred).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.