CVE-2026-105192 · GHSA-w5f2-9q9c-ff4h

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

Risk score: 82/100
CVSS: 9.8 v3.1
Exploit chance (30 days): 0.5%
Published: 7 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is: 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 reque…
Affected: lmcache (pip) >= 0.3.9, < 0.5.6
Fix: Upgrade lmcache to 0.5.6 or later.
Exploitation: Public proof of concept

Why it is Red

CVSS 9.8 critical
Public exploit or proof of concept referenced
Remotely exploitable without logging in
On your watchlist: PyPI

Affected packages

Package	Ecosystem	Vulnerable	Fixed in
lmcache	pip	>= 0.3.9, < 0.5.6	0.5.6

References

Original 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.

Last activity 7 Oct 2026. Patch Forecast updates every hour.