Skip to main content
VulnerabilityPublished Updated

CVE-2025-59953: InternLM lmdeploy · Deserialization of Untrusted Data

Affects InternLM lmdeploySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.10.2 as a priority.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.10.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade lmdeploy and internlm/lmdeploy to 0.10.2.

Affected software

ProductAffectedFixed in
InternLMlmdeployAffected
  • >=0.9.1 <0.10.2
Fixed in
  • 0.10.2
GitHubinternlm/lmdeploypkg:github/internlm/lmdeployOther threatsAffected
  • >=0.9.1 <0.10.2
Fixed in
  • 0.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade lmdeploy to version 0.10.2 or later, which contains the official fix for this vulnerability. No other mitigations are indicated by the vendor advisory.

Description

LMDeploy is a toolkit for compressing, deploying, and serving large language models. Starting in version 0.9.1 and prior to version 0.10.2, the LMdeploy implements an rpc server (AsyncRPCServer in zmq_rpc.py) for supporting the RPC communications. In its core functionality call_and_response(), I found it will directly use the pickles.loads() to deserialize the received messages without any sanitization, hence resulting in a remote code execution vulnerability by this RPC server. Version 0.10.2 contains a patch.

References

Community reviews

Loading reviews…