Skip to main content

Mooncake Store EUVDEUVD-2026-93402

| CVE-2026-106039 MEDIUM
Missing Authorization (CWE-862)
2026-10-06 disclosure@vulncheck.com GHSA-vf47-333j-q4ww
6.9
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed coro_rpc port
  2. Exploit
    Call QueryTask to harvest victim UUIDs
  3. Execution
    Invoke CreateCopyTask/MarkTaskToComplete with stolen UUIDs
  4. Impact
    Hijack task queues and falsify replication records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the Mooncake Store master service's coro_rpc RPC port; no authentication, credentials, or user interaction are needed (PR:N/UI:N), and the victim client UUIDs required to target specific task queues are not a prerequisite the attacker must obtain externally because the unauthenticated QueryTask RPC discloses them directly. The practical limiting factor is network exposure of the coro_rpc port: if the master binds only to localhost or the port sits behind a firewall/trusted-network boundary, remote exploitation is blocked. Affected deployments are Mooncake Store master builds through 0.3.13.post1.

Impact

This is a medium-severity (CVSS 4.0 base 6.9) missing-authorization flaw (CWE-862) whose exploitability signals are favorable to an attacker but whose impact is bounded. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates fully remote, unauthenticated, low-complexity access with no user interaction - the hardest preconditions are already removed - and the design is self-enabling because the UUIDs needed to target victims are themselves disclosed by the unauthenticated QueryTask RPC. However, impact is explicitly limited to low integrity and low availability (VI:L/VA:L) with no confidentiality, no scope change, and no subsequent-system impact, so this is tampering with/hijacking of replication-task state rather than code execution or data theft. No EPSS score, CISA KEV listing, or POC indicator is present in the input, so there is no evidence of active exploitation or weaponization; the only exploitation enabler is the low barrier inherent to the design. Net: a genuine, credible issue for anyone exposing the Mooncake Store master's coro_rpc port to untrusted networks, but not a drop-everything emergency absent exposure - the real priority hinges on whether that port is network-reachable, which the CVE data does not state. One caveat: the input Tags label this 'Authentication Bypass' while the CWE and description describe missing authorization on already-reachable RPCs - a related but distinct class - verify framing against the VulnCheck advisory.

Exploit ScenarioDerived

An attacker with network reachability to a Mooncake Store master's coro_rpc port calls QueryTask (no authentication) to enumerate active replication tasks and harvest legitimate client UUIDs, then replays those UUIDs into CreateCopyTask/CreateMoveTask, FetchTasks, and MarkTaskToComplete to hijack victim task queues and mark replications as complete that never actually ran. No public exploit was identified at time of analysis, but the attack requires only crafted RPC calls against the exposed port and no special tooling given the low attack complexity (AC:L).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Unauthenticated attackers who can reach the Mooncake Store master's coro_rpc port can hijack replication task queues in Mooncake Store master builds through 0.3.13.post1, creating, stealing, and falsely completing replication tasks on behalf of arbitrary victim clients. The affected master RPC handlers (CreateCopyTask, CreateMoveTask, FetchTasks, MarkTaskToComplete) perform no ownership or authorization checks (CWE-862), and the QueryTask RPC discloses the victim client UUIDs needed to target a specific queue, so no credentials, prior knowledge, or user interaction are required. Impact is bounded to integrity and availability (CVSS 4.0 base 6.9; independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, medium severity) - replication bookkeeping can be corrupted and real replication skipped, but confidentiality is unaffected; no public exploit code or CISA KEV listing was identified at time of analysis, and the practical limiting factor is whether the coro_rpc port is exposed beyond localhost or a trusted network boundary.

RemediationAI

No vendor-released patched version is identified in the available data; the advisory points to upstream source at commit 719735896c86b56fabec6cf3e825fb2ea640597a and to issue https://github.com/kvcache-ai/Mooncake/issues/4475, which should be tracked for a fix that adds caller-to-client-UUID authorization on the coro_rpc task-management handlers. Until a patched build is confirmed, treat the coro_rpc port as a trusted-network-only interface: bind the master to a private interface instead of a wildcard address and restrict the port with firewall or security-group rules to the known addresses of legitimate store nodes and clients (trade-off: any node or client outside the allowlist loses connectivity, so the list must be maintained as the cluster scales, and multi-tenant or cross-cluster topologies may not be able to use this control at all). Where network isolation is impractical, place an authenticating proxy or service mesh with per-client mTLS identities in front of the RPC endpoint and, if the codebase is forked internally, enforce server-side checks that task operations are bound to the calling client's UUID rather than trusting the UUID in the request (trade-off: added latency and operational complexity, and any local patch will diverge from upstream behavior). Because a hijacked queue can be marked complete when no copy actually occurred, add monitoring for unexpected bursts of CreateCopyTask, CreateMoveTask, FetchTasks, and MarkTaskToComplete in master logs and metrics, and run out-of-band checksum or data-integrity verification of replicated objects, since silent bookkeeping corruption will otherwise go undetected until a read misses expected data.

Affected VersionsENISA

mooncake 0 ≤0.3.13.post1

Affected Packages

euvd mooncake no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Mooncake (kvcache-ai/Mooncake) is a KVCache-centric disaggregated storage and transfer layer used to serve large language model inference workloads; the Mooncake Store master acts as the control plane that coordinates distributed store segments and orchestrates replication of cached objects between nodes. That control plane is exposed over coro_rpc, a coroutine-based C++ RPC framework, and the affected logic lives in mooncake-store/src/master_service.cpp (approximately lines 12060-12120) with supporting task bookkeeping in mooncake-store/src/task_manager.cpp (lines 113-135). The root cause is CWE-862 (Missing Authorization): the master accepts task-management RPCs without verifying that the caller owns the client UUID it names, and because QueryTask hands out those UUIDs to any caller, the authorization boundary is effectively nonexistent for anyone who can reach the port. The consequence is manipulation of the replication task state machine - task creation, task enumeration, and completion marking - rather than memory corruption or remote code execution, which is consistent with the low integrity and availability impact and the absence of any confidentiality impact in the assessed vector.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Remote unauthenticated RPCs reachable over the network give AV:N/AC:L/PR:N/UI:N; impact is tampering with and hijacking replication tasks, so I:L and A:L with no confidentiality (C:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Mooncake Store master through 0.3.13.post1 contains a missing authorization vulnerability that allows unauthenticated attackers to create, steal, and falsely complete replication tasks via the coro_rpc port. Attackers can invoke CreateCopyTask, CreateMoveTask, FetchTasks, and MarkTaskToComplete with victim client UUIDs disclosed by QueryTask to hijack task queues and record replication that never occurred.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Low
emerging open-source LLM KVCache serving store, niche AI-infra footprint
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy