CVE-2026-105192 LMCache CVE debrief

Who should care

Defenders responsible for LMCache instances, especially those running in multiprocess mode or as root, should assess exposure and prioritize patching or mitigations. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and apply patches or mitigations as available.

Why it matters

Defenders should prioritize verifying exposure of LMCache instances running in multiprocess mode, especially those running as root, and apply patches or mitigations as available due to the critical severity and potential for unauthenticated code execution.

• Unauthenticated code execution as the user the LMCache process runs as
• Potential for privilege escalation if the process runs as root
• Possible disruption of service due to unauthorized code execution

Technical summary

LMCache multiprocess mode opens an unauthenticated ZeroMQ ROUTER, allowing worker processes to 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.

Defensive priority

Defenders should prioritize verifying exposure of LMCache instances running in multiprocess mode, especially those running as root, and apply patches or mitigations as available.

Recommended defensive actions

• Verify LMCache instances running in multiprocess mode and apply patches or mitigations as available
• Restrict access to the transport port (default 5555) to trusted sources
• Monitor for suspicious activity on the transport port
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected product, attack vector, and technical description. The vulnerability affects LMCache instances running in multiprocess mode, especially those running as root. Defenders should verify exposure and prioritize patching or mitigations. The official CVE Program record and NIST NVD detail page provide additional information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.