CVE-2026-119706: LMDeploy 0.9.0 through 0.18.0 Unauthenticated RCE via /update_weights Pickle Deserialization

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 30 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

1%

EPSS score, percentile 63.7 of all scored records. A probability estimated by FIRST, not a report of exploitation.

CISA's SSVC assessment in the CVE record lists exploitation as poc.

How severe?

9.3 Critical

CVSS v4.0 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (1)

Which versions are affected?

Affected

• 0.9.0 through 0.18.0

Versions by product

Source: CISA KEV 2026.10.30, as of 30 Oct 2026; FIRST EPSS, as of 31 Oct 2026; CVE List, as of 1 Nov 2026. About the data.

Description

LMDeploy 0.9.0 through 0.18.0 Unauthenticated RCE via /update_weights Pickle Deserialization

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.

Source: CVE List, as of 1 Nov 2026. About the data.

What to do

Advisories and patches

• github.com (Patch, Issue tracking)

This summary is based on the CVE record as of 1 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 1 Nov 2026. About the data.

Timeline