Live › vulnerability › GHSA-vv44-hjm2-qw2f
Go to dashboardThis advisory is a withdrawn duplicate of GHSA-w5f2-9q9c-ff4h and was never a separate issue. The original text says LMCache's multiprocess mode exposes an unauthenticated ZeroMQ socket that calls pickle.loads on incoming messages, so one crafted message to port 5555 runs code as the LMCache process user.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| lmcache | pypi | >= 0.3.9, < 0.5.6 | – |
Unknown from the sources.
Use the advisory this one duplicates, GHSA-w5f2-9q9c-ff4h, and upgrade pypi:lmcache to a version at or above 0.5.6 (the range given is >= 0.3.9, < 0.5.6).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This advisory has been withdrawn because it is a duplicate of GHSA-w5f2-9q9c-ff4h. This link is maintained to preserve external references.
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.
This page as .md · .json · in your agent: get_signal("GHSA-vv44-hjm2-qw2f")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.