Cve 2026 105192 Lmcache Unauthenticated Remote Code Execution Via Zeromq Deserialization Cve 2026 105192

No standalone public exploit has been published in open research repositories at the time of writing. Our threat intelligence pipeline monitors GitHub, Exploit-DB, and Nuclei feeds continuously. Verified PoCs will be automatically integrated here upon discovery.

CVE-2026-105192 exposes LMCache deployments to unauthenticated remote code execution, leveraging a critical deserialization vulnerability within its multiprocess communication. A single crafted ZeroMQ message can grant an attacker root-level command execution on affected systems, leading to complete system compromise and lateral network pivoting.

Vulnerability Root Cause & Flaw Mechanism

This critical vulnerability originates in LMCache’s multiprocess, or distributed, mode, which establishes an unauthenticated ZeroMQ ROUTER socket. This socket facilitates worker process registration and KV cache block sharing. The core flaw lies in the premature deserialization of untrusted data: messages received on this ZeroMQ socket are encoded using msgpack. Critically, extension code 1 within these msgpack messages is passed directly to DeviceIPCWrapper.Deserialize . This function, in turn, invokes pickle.loads while the server is still decoding request arguments, prior to any handler execution. This sequence bypasses authentication and input validation, allowing arbitrary Python objects to be deserialized and executed on the host system. The mechanical failure is a classic insecure deserialization of untrusted data, specifically via Python’s pickle module, triggered by a specific msgpack extension code within the ZeroMQ communication stream.

Attack Prerequisites & Threat Vector

Exploitation of CVE-2026-105192 requires no prior authentication. The primary attack vector involves sending a single, specially crafted ZeroMQ DEALER message to the LMCache transport port, which defaults to 5555. Network accessibility is paramount: by default, the transport binds to localhost , limiting the attack surface to local privilege escalation or access from an already compromised host. However, multi-node deployments often configure LMCache with the --host argument, exposing a routable address. In such configurations, the vulnerability becomes remotely exploitable over the network. The code execution occurs as the user running the LMCache process. A significant operational risk is that official container images for LMCache run this process as root , elevating successful exploitation to unauthenticated remote root-level command execution.

Detection, Log Analysis & Threat Hunting

Detection efforts should focus on anomalous network traffic and process activity. SOC analysts should monitor network flows for unexpected ZeroMQ DEALER messages directed at LMCache instances, specifically targeting TCP port 5555. Look for unusual message sizes or patterns indicative of msgpack encoding with extension code 1. While specific log entries for pickle.loads invocation or DeviceIPCWrapper.Deserialize failures are not detailed in the advisory, monitoring Python process logs for unexpected errors, child process spawning, or resource utilization spikes from the LMCache process user (especially root ) could indicate compromise. For asset owners and penetration testers, a targeted Shodan dork to identify potentially exposed instances is: port:5555 "ZeroMQ" or port:5555 "LMCache" . Further reconnaissance would involve attempting to identify LMCache service banners or specific ZeroMQ handshake responses.

Defensive Hardening & Mitigation

Immediate defensive hardening measures are critical for systems awaiting a vendor patch. Implement strict network segmentation and firewall rules to restrict access to LMCache’s transport port (TCP 5555). Unless multi-node functionality is explicitly required, ensure the LMCache process binds only to localhost and avoid using the --host argument with routable addresses. For necessary multi-node deployments, restrict peer connections to trusted IP ranges via host-based firewalls or network ACLs. Furthermore, run the LMCache process with the lowest possible privileges; avoid running it as root , especially within containerized environments, to mitigate the impact of successful exploitation. As of the published date (October 7, 2026), no public PoC is available, and information regarding a vendor patch status is pending. Organizations should monitor official LMCache channels for patch releases.

Related Vulnerabilities

CVE-2026-76747: AOS-S Buffer Overflow: Unauthenticated Remote Memory Exposure and DoS

CVE-2026-79798: ClearPass Policy Manager SQLi Enables Arbitrary Database Command Execution

CVE-2026-79801: A missing integrity verification vulnerability in the cli…

TheHackerWire Threat Intel Team