Skip to main content
Vulnerability Database/CVE-2026-106041

CVE-2026-106041: Mooncake Store Auth Bypass Vulnerability

CVE-2026-106041 is an authentication bypass flaw in Mooncake Store that allows unauthenticated attackers to inject malicious replicas and poison disk-tier reads. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106041 Overview

CVE-2026-106041 is a missing authorization vulnerability [CWE-862] affecting Mooncake Store master through version 0.3.13.post1. The flaw resides in the NotifyOffloadSuccess Remote Procedure Call (RPC) handler within master_service.cpp. Unauthenticated attackers can inject completed LOCAL_DISK replicas by mounting a local disk segment with a self-chosen client UUID. Attackers then attach replicas pointing at attacker-controlled endpoints to serve poisoned disk-tier reads and fake key existence responses. Mooncake Store is a distributed key-value cache used in large language model (LLM) inference pipelines, so poisoned reads directly affect model-serving integrity.

Critical Impact

Network-reachable attackers can poison cache reads and fabricate key existence without authentication, undermining integrity of the disk tier.

Affected Products

  • Mooncake Store master branch
  • Mooncake Store versions up to and including 0.3.13.post1
  • Deployments exposing the master_service RPC endpoint on the network

Discovery Timeline

  • 2026-10-06 - CVE-2026-106041 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-106041

Vulnerability Analysis

Mooncake Store exposes an RPC surface through its master service to coordinate replica placement across memory, disk, and remote tiers. The NotifyOffloadSuccess RPC is intended for trusted storage workers to signal that an offload operation finished and that a new LOCAL_DISK replica is ready for lookup. The handler in master_service.cpp does not validate whether the caller is an authorized worker. Any network-reachable client can invoke the RPC, register a mounted local disk segment under an arbitrary client UUID, and attach replica entries referencing endpoints the attacker controls. Subsequent cache reads routed to that replica retrieve attacker-supplied bytes, and key existence probes return true for keys the attacker chose. In LLM inference contexts this translates to tampered key-value cache content being fed into model execution paths.

Root Cause

The root cause is missing authorization on an RPC that mutates cluster metadata. The NotifyOffloadSuccess path accepts caller-provided client UUIDs and replica descriptors without verifying worker identity, membership, or ownership of the referenced segment. See the referenced master_service.cpp source for the affected handler.

Attack Vector

Exploitation requires network access to the Mooncake master RPC port. No credentials, user interaction, or prior foothold are required. An attacker scripts an RPC client that mounts a LOCAL_DISK segment, invokes NotifyOffloadSuccess for chosen keys, and advertises endpoints under attacker control. Victim consumers reading those keys receive poisoned payloads. See the VulnCheck advisory and GitHub issue #4479 for additional detail.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-106041

Indicators of Compromise

  • Unexpected NotifyOffloadSuccess RPC calls originating from source IPs that are not registered Mooncake storage workers.
  • LOCAL_DISK replicas registered with client UUIDs that do not match the provisioned worker inventory.
  • Replica endpoint fields pointing to hosts or ports outside the known Mooncake data-plane subnet.
  • Downstream LLM inference anomalies, such as cached keys returning content inconsistent with the producing workload.

Detection Strategies

  • Enable verbose RPC logging on the Mooncake master service and alert on NotifyOffloadSuccess invocations lacking a matching prior mount from a trusted worker.
  • Reconcile the live replica table against the authoritative worker roster on a scheduled interval and flag mismatches.
  • Deploy network segmentation telemetry to identify any client reaching the master RPC port from outside the designated worker subnet.

Monitoring Recommendations

  • Capture flow logs for the master service port and alert on new source addresses.
  • Monitor cache integrity metrics such as read-after-write mismatches and sudden shifts in KeyExists true-rate.
  • Forward Mooncake master logs to a centralized logging pipeline for correlation with host and network telemetry.

How to Mitigate CVE-2026-106041

Immediate Actions Required

  • Restrict network reachability of the Mooncake master RPC port to known worker IP addresses using firewall or network policy rules.
  • Audit the current replica table for LOCAL_DISK entries whose client UUIDs or endpoints do not match provisioned workers and purge suspicious records.
  • Rotate or re-provision affected cache contents and revalidate downstream inference outputs that may have consumed poisoned reads.

Patch Information

No fixed release is identified in the published advisory at the time of writing. Track the upstream Mooncake GitHub repository and GitHub issue #4479 for a vendor fix beyond 0.3.13.post1.

Workarounds

  • Place the master service behind a mutually authenticated transport, such as mutual TLS terminated by a sidecar proxy, so untrusted callers cannot reach the RPC handler.
  • Enforce Kubernetes NetworkPolicy or equivalent L4 controls that permit only worker pods to connect to the master RPC port.
  • Run Mooncake on a dedicated private network segment with no ingress from tenant workloads or user-facing systems.
bash
# Example iptables rule: allow only known worker IPs to reach the master RPC port
iptables -A INPUT -p tcp --dport <MOONCAKE_MASTER_RPC_PORT> -s <WORKER_SUBNET> -j ACCEPT
iptables -A INPUT -p tcp --dport <MOONCAKE_MASTER_RPC_PORT> -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.