On October 7, 2026, JFrog Security Research disclosed CVE-2026-105192: a maximum-severity flaw in LMCache — the open-source key-value cache layer bolted onto vLLM inference servers. In multiprocess (distributed) mode, a single unauthenticated message to the ZeroMQ transport socket executes attacker code through Python pickle deserialization. No fixed release exists, a public proof-of-concept is available, and the official container images run as root. This free CVE check tool tells you if you're at risk. No signup, nothing installed.
Key figure: CISA's Known Exploited Vulnerabilities catalog listed 1,748 entries as of October 16, 2026, every one confirmed exploited in the wild (CISA KEV catalog, version 2026.10.16).
CVE-2026-105192 is urgent cybersecurity news because it is a pickle-deserialization RCE in LMCache with no patch available — attackers who reach the service can execute arbitrary code. Unpatchable flaws demand workarounds: network isolation, strict input validation, and active monitoring. The 30-second check above tells you whether you are exposed.
127.0.0.1, firewall port 5555 (the default), or lock it down with a Kubernetes NetworkPolicy. This is the single highest-value mitigation.--user, runAsUser) so a hit doesn't become host takeover.This page checked one CVE. Rogue-Agent Defense watches agent and AI-infrastructure estates for unsafe deserialization, prompt injection, and tool-misuse — the patterns this attack uses.
Drop a live version-checker into your blog, docs, or forum post — three lines of HTML.
Get the embed codeCheck the version with pip show lmcache or your container image tag: versions 0.3.9 through 0.5.5 (plus 0.5.6 release candidates) contain the flaw, and no patched release exists yet. Then check the bind: the flaw is only remotely reachable when multiprocess mode's ZeroMQ socket binds a routable address (via --host or Kubernetes hostNetwork). Localhost-bound deployments are not reachable from the network.
No. The ZeroMQ ROUTER socket has no authentication, no encryption, and no message verification. One crafted DEALER message to the transport port (default 5555) triggers Python pickle deserialization during request-argument decoding — before any handler runs — executing the sender's code as the LMCache process user.
Contain it at the network layer: bind the transport to 127.0.0.1, firewall port 5555, never run the official image as root, segment the cache tier away from secrets and model weights, and rotate credentials the process could reach. Watch for the fixed release and re-run this check when it lands.
A CVE checker is a free tool that tells you whether your software is affected by a published CVE — a publicly known cybersecurity vulnerability. It compares your version or configuration against the official advisory and gives you a patched, vulnerable, or unknown verdict in about 30 seconds.
Find your exact version number, then compare it against the vendor's security advisory or the NVD entry for the CVE. The fastest way is a CVE checker built for that product: paste your version and get an instant verdict against the published version tables.
You are affected when you run a vulnerable version and the vulnerable component is reachable or enabled — for example, open sign-ups, an exposed management port, or a vulnerable app installed. A CVE checker gives you the version verdict in seconds; the advisory's conditions tell you whether that verdict means real exposure.