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

CVE-2026-104433: Mooncake Transfer Engine DoS Vulnerability

CVE-2026-104433 is a denial of service flaw in Mooncake transfer engine that lets attackers crash the service remotely. This post covers the technical details, affected versions, security impact, 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-104433 Overview

CVE-2026-104433 is an out-of-bounds read vulnerability in the Mooncake transfer engine before version 0.3.12. The flaw resides in the readString function of include/common.h and is triggered by a zero-length handshake frame. Unauthenticated remote attackers can connect to the handshake port, which listens on all interfaces, and send an eight-byte frame to terminate the hosting process. Affected deployments include SGLang inference servers and other AI workloads that embed the Mooncake transfer engine for peer-to-peer key-value cache transfer. The vulnerability is classified under CWE-125: Out-of-bounds Read.

Critical Impact

Unauthenticated network attackers can crash Mooncake-backed inference services with a single 8-byte handshake frame, disrupting hosted LLM workloads.

Affected Products

  • Mooncake transfer engine versions prior to 0.3.12
  • SGLang inference servers embedding vulnerable Mooncake builds
  • Any application linking mooncake-transfer-engine with the P2P handshake listener exposed

Discovery Timeline

  • 2026-10-03 - CVE-2026-104433 published to the National Vulnerability Database (NVD)
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-104433

Vulnerability Analysis

The Mooncake transfer engine exposes a peer-to-peer handshake listener for coordinating key-value cache transfers between inference nodes. During handshake processing, the readString helper in mooncake-transfer-engine/include/common.h reads a length prefix from the socket and then attempts to read that many bytes into a buffer. When the attacker-supplied length is zero, the function allocates a zero-sized vector and subsequently performs an out-of-bounds read while interpreting the result. The faulty access terminates the hosting process, taking the inference service offline.

The listener binds to all interfaces by default. Any network-reachable attacker can reach the port and submit the eight-byte handshake frame without authentication. Exploitation requires no privileges, no user interaction, and only trivial protocol knowledge.

Root Cause

The root cause is missing validation of the length field decoded from the handshake frame. The pre-patch code paths through readString without rejecting a zero-length value, allowing downstream logic to dereference an empty buffer. The fix in commit c142b40 short-circuits the function when length == 0 and returns an empty string, preventing the out-of-bounds read.

Attack Vector

An unauthenticated remote attacker establishes a TCP connection to the Mooncake handshake port and transmits an 8-byte frame declaring a zero-length string payload. readString processes the frame, triggers the out-of-bounds read, and crashes the parent process. Repeated connections produce a sustained denial-of-service condition against the inference server.

c
         return {type, ""};
     }
 
+    if (length == 0) {
+        LOG(ERROR) << "readString: zero length from socket";
+        return {type, ""};
+    }
+
     std::string str;
     std::vector<char> buffer(length);
     n = readFully(fd, buffer.data(), length);

Source: GitHub commit c142b40 — the patch adds a zero-length guard to readString and corrects related error-path safety issues, including a freeaddrinfo leak and a null dereference in sendNotifyByID.

Detection Methods for CVE-2026-104433

Indicators of Compromise

  • Unexpected termination of SGLang or other Mooncake-backed inference processes with no accompanying model workload error
  • Short-lived TCP connections to the Mooncake handshake port from unexpected source addresses
  • Repeated process restarts of the inference container shortly after inbound connections on the handshake listener

Detection Strategies

  • Alert on crash loops or supervisor restarts of inference services that bind the Mooncake transfer engine
  • Correlate inbound TCP sessions carrying exactly 8 bytes of payload to the handshake port with subsequent process exits
  • Deploy network signatures that flag handshake frames declaring a zero-length string field

Monitoring Recommendations

  • Collect stderr and stdout from Mooncake-backed services and search for readString error logging or abrupt termination
  • Monitor host-level process exit codes and signal-based terminations on nodes that run SGLang inference workloads
  • Capture flow telemetry on the handshake listener and baseline expected peer sources to detect anomalous connections

How to Mitigate CVE-2026-104433

Immediate Actions Required

  • Upgrade the Mooncake transfer engine to version 0.3.12 or later across all inference nodes
  • Restrict network reachability of the handshake port to trusted peer addresses using host or network firewalls
  • Audit SGLang and other dependent deployments to confirm the embedded Mooncake build has been updated

Patch Information

The fix is included in Mooncake 0.3.12 and shipped in commit c142b40590259360196d8e504b2193382529e7b4. The commit adds a length validation branch to readString, closes a freeaddrinfo leak, and guards against a null segment descriptor dereference in TransferEngineImpl::sendNotifyByID. Additional context is available in the VulnCheck advisory and the upstream issue discussion.

Workarounds

  • Bind the Mooncake handshake listener to a loopback or private interface instead of all interfaces where configuration permits
  • Place inference nodes behind a network segment reachable only by trusted transfer peers
  • Use iptables, nftables, or cloud security groups to allow handshake traffic only from known peer IP addresses
bash
# Restrict the Mooncake handshake port to trusted peer subnets
sudo iptables -A INPUT -p tcp --dport <mooncake-handshake-port> -s <trusted-peer-cidr> -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <mooncake-handshake-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.