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.
CVE-2025-59953
CRITICALPre-NVD 9.89.8—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 51%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available
Remote code execution via unsafe pickle deserialization in the LMDeploy ZMQ RPC server · Advisory · InternLM/lmdeploy · GitHub
https://github.com/InternLM/lmdeploy/security/advisories/GHSA-5h8j-6crg-7rmwgithub_release Patch Available
v0.10.2
Patch available: InternLM/lmdeploy v0.10.2
https://github.com/InternLM/lmdeploy/releases/tag/v0.10.2Vendor Advisories for CVE-2025-59953(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| lmdeploy | 0.10.0, 0.10.1, 0.9.1, 0.9.2, 0.9.2.post1 | 0.10.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 22:10 UTCEG score recompute
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 18:32 UTCEG score recompute
- 2026-09-18 18:15 UTCEG score recompute
- 2026-09-17 21:57 UTCEG score recompute
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 16:31 UTCEG score recompute
- 2026-09-16 15:45 UTCEG score recompute
- 2026-09-16 15:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2025-59953?
CVE-2025-59953 is a critical vulnerability published on September 16, 2026. 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 zmqrpc.py) for supporting the RPC communications. In its core functionality calland_response(), I…
When was CVE-2025-59953 disclosed?
CVE-2025-59953 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-59953 actively exploited?
CVE-2025-59953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.3% of all scored CVEs.
What is the CVSS score of CVE-2025-59953?
CVE-2025-59953 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-59953?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-59953, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-59953
Is Your Infrastructure Affected by CVE-2025-59953?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.