LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport (Critical severity, CVE-2026-105192)
A critical-severity advisory for the pip package lmcache is fixed in version 0.5.6.
Key points
- lmcache (pip) has a critical flaw.
- Tracked as CVE-2026-105192.
- Version 0.5.6.
Maintainers of lmcache, a package in the pip ecosystem, have published a critical-severity security advisory (CVE-2026-105192): LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport.
At a glance
- Advisory
- GHSA-w5f2-9q9c-ff4h
- CVE
- CVE-2026-105192
- Package
- lmcache (pip)
- Severity
- Critical
- Patched in
- 0.5.6
What is the issue?
The GitHub-reviewed advisory explains: 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
Affected versions
| Ecosystem | Package | Vulnerable | Patched |
|---|---|---|---|
| pip | lmcache | >= 0.3.9, < 0.5.6 | 0.5.6 |
The advisory lists a CVSS score of 9.8.
How to fix it
- Upgrade the affected package to the first patched version listed above.
- Rebuild and redeploy applications that bundle the vulnerable dependency.
- Run your dependency scanner (npm audit, pip-audit, Dependabot) to find transitive uses.
- Review the advisory references for workaround details if you cannot upgrade yet.
What to do and how to stay safe: CVE-2026-105192
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-105192?
CVE-2026-105192 is a security vulnerability in lmcache (pip).
Which version fixes CVE-2026-105192?
The fix is in version 0.5.6.
