CVE-2026-105192
LMCache Unauthenticated RCE in multiprocess mode via pickle deserialization
- Critical 9.8
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.
Key facts
- Published
- 7 Oct 2026
- Last changed
- 29 Oct 2026
- Assigned by
- JFROG
- EPSS
- 1.024% likely to be exploited in the next 30 days, higher than 64.12% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: yes; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 9.8CVSS 3.1, Criticalfrom the CNA (JFROG)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
What to do
- 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.CNA solution statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| LMCache | LMCache |
|
Timeline
- 29 Oct 2025 LMCache v0.3.9 ships the multiprocess ZMQ transport and the pickle-backed msgpack extension
- 7 Oct 2026 Published
- 12 Oct 2026 PR #5644 merged: pickle removed from device IPC descriptors
- 14 Oct 2026 LMCache v0.5.6 released, the first version that includes the fix
Weakness
References
- LMCache repository
- lmcache on PyPI
- DeviceIPCWrapper.Deserialize calls pickle.loads (v0.5.5)
- msgpack extension code 1 decoded with pickle (v0.3.9)
- JFrog Security Research advisory JFSA-2026-001694382
- LMCache update on CVE-2026-105192
- GHSA-w5f2-9q9c-ff4h
- PR #5644: replace pickle in device IPC descriptors
- LMCache v0.5.6
- PR #5684: bind example Kubernetes deployment to localhost
- PR #5685: run official images as a non-root user