TL;DR: LMCache and Mooncake disclosures show AI inference cache services and adjacent management APIs can be exposed through unauthenticated, network-reachable flaws, NetFoundry found. Identity-first reachability keeps those services invisible until an authorised workload is allowed to connect.
Editorial analysis by NHI Mgmt Group, based on content published by NetFoundry: “Reachability Watch: An AI Cache Server That Runs Any Script It’s Sent, and Nearly 440 New CVEs”.
By the numbers:
- Nearly 440 new network-exploitable CVEs were published October 2–8, 2026.
- 52 cleared our severity bar (CVSS 8.6+), including 2 rated a perfect 10.0.
- 15 WordPress plugins accounted for 15 of the week's 52 high-severity CVEs.
Key questions
Q: Why do default-open management ports create such high risk in AI infrastructure?
A: Because they collapse the trust boundary between a trusted cluster and a shared production network.
Q: What are the signs that an AI serving component is overexposed?
A: Look for unauthenticated HTTP endpoints, management APIs that bind to all interfaces, services that accept code or metadata changes without identity checks, and cache systems colocated with model servers on the same network path.
A: Start by making reachability conditional on policy, not on network location.
Practitioner guidance
- Constrain exposed AI cache services before patching windows open Place cache, metadata and control-plane services behind explicit policy so they are unreachable from the general network until a verified workload is authorised.
- Inventory every service that listens on all interfaces Find services bound to 0.0.0.0 or equivalent defaults, then classify which of them handle code, metadata or management operations.
- Separate execution-capable endpoints from serving paths Do not let script execution, metadata mutation and inference traffic share the same unguarded surface, especially in shared clusters.
Bottom line: AI inference caches and their adjacent management services are now part of the attack surface, not just an internal performance layer.
Glossary terms: Inference Cache, Identity-First Reachability, Network-Exploitable CVE, Workload Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Network reachability has become a governance control for AI infrastructure. The article shows that unauthenticated flaws in cache and management services matter because the service is exposed before any identity check happens. That shifts the control problem from patching alone to whether a workload is even present on the network in the first place. Practitioners should treat exposure as a decision, not a default.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should teams do when a vulnerable AI cache service cannot be patched immediately?
A: Treat the service as unreachable until policy allows a specific workload to call it. That means removing public or broad network access, constraining who can connect, and keeping the service off the general network path while a fix is pending. This limits exploitation even when the code defect still exists.
👉 Read our full editorial: AI inference caches expose a new network attack surface