critical

CVE-2026-105192

LMCache: Remote code execution via unsafe deserialization in multiprocess mode transport

Published 7 Oct 2026Modified 7 Oct 2026CWE 306, 502

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by GHSA.

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.

Affected packages and fixed versions

Source	Package	Fixed in
pip::GitHub Security Advisory pip	lmcache	0.5.6
chainguard	kserve-huggingfaceserver-cuda-13.3, lmcache-cuda-13.0	0.21.0-r6 and 1 more

Show all 3 entries from 2 sources

Source	Package	Fixed in
pip::GitHub Security Advisory pip	lmcache	0.5.6
chainguard	kserve-huggingfaceserver-cuda-13.3	0.21.0-r6
chainguard	lmcache-cuda-13.0	0.5.6-r0

References

All 14 references

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs