Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

LMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploy

CVE-2025-59953GHSA-5h8j-6crg-7rmw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (lmdeploy 0.10.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI lmdeploy

    Affected
    >= 0.9.1, < 0.10.2
    Fixed in
    0.10.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-59953: 0.88% estimated exploitation activity in the next 30 days; percentile 59.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description The LMdeploy implements an rpc server (AsyncRPCServer in zmqrpc.py) for supporting the RPC communications. In its core functionality callandresponse(), 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. Proof of Concept Step1: The victim user starts a RPC server that connects to its network interface. We give our example code (server.py) in the attachment, you can reproduce directly with server.py. Step2: The attacker can then send malicious pickle dump data to the remote RPC address for the attack. We give a example to show how can an attacker acquire a command shell: <img width="832" height="324" alt="image" src="https://github.com/user-attachments/assets/03b9654d-e25b-4e93-903a-2aae8b12e704" / In this example, attacker modifies AsyncRPCClient and send a request containing malicious pickle dump data to let the victim execute command…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-5h8j-6crg-7rmw

  2. Revision 2 · amended ·

    Amended from osv record GHSA-5h8j-6crg-7rmw

  3. Revision 1 · created ·

    Published from ghsa record GHSA-5h8j-6crg-7rmw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59953

Advisory: LMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploy
IDs: CVE-2025-59953, GHSA-5h8j-6crg-7rmw
Record: https://patchnext.com/advisories/cve-2025-59953 (revision 3, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: lmdeploy 0.10.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lmdeploy: affected >= 0.9.1, < 0.10.2; fixed in 0.10.2

## Suggested inspection (read-only)
- `python -m pip show lmdeploy`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lmdeploy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5h8j-6crg-7rmw (GitHub-reviewed advisory GHSA-5h8j-6crg-7rmw lists affected ranges: PyPI lmdeploy >=0.9.1 <0.10.2)
- Verified: https://osv.dev/vulnerability/GHSA-5h8j-6crg-7rmw (OSV record GHSA-5h8j-6crg-7rmw lists affected ranges: PyPI lmdeploy >=0.9.1 <0.10.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…