Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
LMCache versions 0.3.9 through 0.5.5 (and the 0.5.6 release candidates) are affected when multiprocess mode binds its unauthenticated ZeroMQ transport to a routable address. An attacker who can reach the transport port (5555 by default) can send one crafted message that runs arbitrary code with the privileges of the LMCache process. Upgrade to LMCache 0.5.6, which replaces the unsafe deserialization; until then, keep the transport on localhost or restrict port 5555 with firewall rules.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA (JFROG) |
- CISA KEV Not listed.
- EPSS 0.010, the 63rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w5f2-9q9c-ff4h
- OSV: GHSA-w5f2-9q9c-ff4h
- github.com/LMCache/LMCache/security/advisories/GHSA-w5f2-9q9c-ff4h
- nvd.nist.gov/vuln/detail/CVE-2026-105192
- github.com/LMCache/LMCache/pull/5644
- github.com/LMCache/LMCache/pull/5684
- github.com/LMCache/LMCache/pull/5685
- github.com/LMCache/LMCache/commit/160b6dec469edb765efd1fad42aca5a438b08bb5
- github.com/LMCache/LMCache/commit/62f74c417dfe1ba56761733fd25dc8209a192f20
- github.com/LMCache/LMCache/commit/767c7e367bbdc357c445cf7bd2ed259cff8d5865
- blog.lmcache.ai/en/2026/10/13/an-update-on-cve-2026-105192
- github.com/LMCache/LMCache
- github.com/LMCache/LMCache/blob/v0.3.9/lmcache/v1/multiprocess/custom_types.py
- github.com/LMCache/LMCache/blob/v0.5.5/lmcache/v1/platform/base/ipc_wrapper.py