جزئیات آسیب‌پذیری

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.

• https://github.com/LMCache/LMCache product
• https://pypi.org/project/lmcache/ product
• https://github.com/LMCache/LMCache/blob/v0.5.5/lmcache/v1/platform/base/ipc_wrapper.py technical-description
• https://github.com/LMCache/LMCache/blob/v0.3.9/lmcache/v1/multiprocess/custom_types.py technical-description
• https://research.jfrog.com/vulnerabilities/lmcache-is-vulnerable-to-unauthenticated-remote-code-execution-via-pickle-deserialization-on-the-multiprocess-zmq-transport-cve-2026-105192-jfsa-2026-001694382/ vendor-advisory
• https://blog.lmcache.ai/en/2026/10/13/an-update-on-cve-2026-105192/ vendor-advisory
• https://github.com/LMCache/LMCache/security/advisories/GHSA-w5f2-9q9c-ff4h vendor-advisory
• https://github.com/LMCache/LMCache/pull/5644 patch
• https://github.com/LMCache/LMCache/releases/tag/v0.5.6 patchrelease-notes
• https://github.com/LMCache/LMCache/pull/5684 mitigation
• https://github.com/LMCache/LMCache/pull/5685 mitigation