LMCache
LMCache Unauthenticated RCE in multiprocess mode via pickle deserialization
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.3.9, < 0.5.6
Fixed in 0.5.6
Mitigation
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.
References
- Vendor advisory research.jfrog.com/vulnerabilities/lmcache-is-vulnerab…
- Vendor advisory blog.lmcache.ai/en/2026/10/13/an-update-on-cve-2026…
- Vendor advisory github.com/LMCache/LMCache/security/advisories…
4 more
Timeline
Days relative to CVE publicationFirst public PoC 20 h after publication; not in CISA KEV. First PoC: rxsklife/CVE-2026-105192 (created 8 Oct 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| rxsklife/CVE-2026-105192 | 8 Oct 2026 +20 h | backfilled | 0 | PoC |
| basesixtythree/B63-POC-CVE-2026-105192 | 1 Nov 2026 +25 d | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.