<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lmcache on CuraSec</title><link>https://curasec.metacog.co.kr/tags/lmcache/</link><description>Recent content in Lmcache on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 17:48:59 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/lmcache/index.xml" rel="self" type="application/rss+xml"/><item><title>Unpatched RCE in LMCache Exposes vLLM AI Infrastructure</title><link>https://curasec.metacog.co.kr/insights/2026-10-07-unpatched-critical-lmcache-flaw-lets-unauthenticated-attacke/</link><pubDate>Wed, 07 Oct 2026 17:48:59 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-07-unpatched-critical-lmcache-flaw-lets-unauthenticated-attacke/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Unpatched critical unauthenticated RCE in LMCache multiprocess mode with no fix available; if running vLLM or any LMCache deployment, immediately disable multiprocess mode or network-isolate the cache server (firewall ZeroMQ port) until a patched release ships.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> No IOCs or confirmed active exploitation reported, but organizations running LLM inference infrastructure should create detections for anomalous process spawning or unexpected inbound connections on LMCache/vLLM nodes; start collecting relevant host and network logs from AI compute clusters now.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Highlights emerging attack surface in enterprise AI infrastructure; no immediate leadership action required, but useful context for AI security posture reviews and vendor risk assessments if LLM serving software is in scope.&lt;/li>
&lt;/ul></description></item></channel></rss>