CVE-2026-105192

LMCache Unauthenticated RCE in multiprocess mode via pickle deserialization

Published Oct 7, 2026 CVSS 3.1 · 9.8 Critical EPSS 1.0% KEV · Not listed
Description
LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. Messages on that socket are msgpack. Extension code 1 is passed to DeviceIPCWrapper.Deserialize, which calls pickle.loads, while the server is still decoding request arguments and before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The decode path shipped in v0.3.9 and is present through v0.5.5, including the v0.5.6 release candidates. v0.5.6, published on 2026-10-14, removes pickle.loads from this path.

Analysis

AI-generated

Technical impact

LMCache’s distributed mode opens an unauthenticated ZeroMQ ROUTER socket on the default port 5555 so workers can register and share cache blocks. The server first decodes incoming MessagePack messages before executing any handler. If a payload contains Extension Code 1, DeviceIPCWrapper.Deserialize calls pickle.loads, allowing arbitrary Python code to run. An attacker can send such a crafted ZMQ DEALER message to the transport port, causing the LMCache process to execute their code. Because the official container images run as root, the attacker obtains full system privileges. The vulnerability therefore permits remote code execution without authentication.

Affected Systems

LMCache versions 0.3.9 through 0.5.5 are vulnerable when distributed mode is enabled over a routable interface and run as root. Deployments using these versions that run as non‑root or that disable distributed mode are not affected. Versions 0.5.6 and later have removed the pickle.loads vulnerability and are not affected.

Risk and Exploitability

With a CVSS score of 9.8 the flaw is critical. The EPSS score is 0.00772, indicating a very low but non‑zero exploitation probability, but the lack of authentication, combined with the default local binding on port 5555, provides an uncomplicated local exploitation path. If an operator exposes the port to external networks, remote attackers can also leverage the vulnerability. The flaw is not listed in CISA's KEV catalog, indicating no widely known public exploits, yet the conditions make it highly exploitable in practice.

Remediation

Vendor Solution

Upgrade to LMCache 0.5.6 or later. That release replaces pickle in device IPC descriptors with versioned, typed MessagePack descriptors. Descriptors are validated before use, the wrapper type is chosen from a fixed local allowlist, and there is no pickle fallback. The change covers the ZeroMQ and gRPC paths. The wire format changed, so upgrade workers and servers together. The fix is PR #5644 and it is in the v0.5.6 tag. PR #5684, which binds the example Kubernetes deployment to localhost, and PR #5685, which runs the official images as a non-root user, were merged after the v0.5.6 tag was cut and are included in v0.5.7rc2. The v0.5.6 example deployment still passes --host 0.0.0.0, and the v0.5.6 images still run as root.


OpenCVE Recommended Actions

  • Upgrade LMCache to a release that disables or protects the pickle deserialization routine
  • If an update is not immediately possible, disable the distributed mode by configuring LMCache to run in single‑process mode or by removing any ZeroMQ bind parameters; additionally, bind the socket only to localhost and restrict access with a firewall
  • Run the LMCache process under a non‑root user and limit its container privileges
  • If ZeroMQ authentication is supported, enable it or use an alternative signed messaging protocol to prevent unauthenticated connections

Generated by OpenCVE AI on October 29, 2026 at 12:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-w5f2-9q9c-ff4h LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport
History
Type Values Removed Values Added
Description LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. Messages on that socket are msgpack. Extension code 1 is passed to DeviceIPCWrapper.Deserialize, which calls pickle.loads, while the server is still decoding request arguments and before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. Messages on that socket are msgpack. Extension code 1 is passed to DeviceIPCWrapper.Deserialize, which calls pickle.loads, while the server is still decoding request arguments and before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The decode path shipped in v0.3.9 and is present through v0.5.5, including the v0.5.6 release candidates. v0.5.6, published on 2026-10-14, removes pickle.loads from this path.
References
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Lmcache
Lmcache lmcache
Vendors & Products Lmcache
Lmcache lmcache
Type Values Removed Values Added
Description LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. Messages on that socket are msgpack. Extension code 1 is passed to DeviceIPCWrapper.Deserialize, which calls pickle.loads, while the server is still decoding request arguments and before the handler runs. A single unauthenticated ZMQ DEALER message to the transport port (default 5555) therefore executes code as the user the LMCache process runs as. Official container images run that process as root. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect.
Title LMCache Unauthenticated RCE in multiprocess mode via pickle deserialization
Weaknesses CWE-306
CWE-502
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
JFROG
Published
Updated
Oct 29, 2026, 10:24 AM
Reserved
Oct 4, 2026, 11:50 AM
Status
Deferred
Published
Oct 7, 2026, 10:17 AM
Modified
Oct 29, 2026, 11:17 AM