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-107820 Overview
CVE-2026-107820 is a pre-authentication denial-of-service vulnerability in x64dbg-MCP Server, a native Model Context Protocol (MCP) plugin for the x64dbg debugger. The server exposes debugger functionality over HTTP and, in versions prior to 1.2, binds to 0.0.0.0 by default. The flaw resides in parseContentLength() within src/core/mcp_server.zig, which accepts an unbounded Content-Length header value. That value is then used in unchecked usize addition inside wsRecv() before token authentication runs. The weakness is classified as an integer overflow [CWE-190].
Critical Impact
An unauthenticated network attacker can send a crafted Content-Length header to crash the entire x64dbg process, terminating any live debugging session.
Affected Products
- x64dbg-MCP Server versions prior to 1.2
- Deployments using the default 0.0.0.0 network bind
- Debug and ReleaseSafe builds of the Zig-based plugin
Discovery Timeline
- 2026-10-09 - CVE-2026-107820 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-107820
Vulnerability Analysis
The vulnerability affects the HTTP request parsing path in the x64dbg-MCP Server. The function parseContentLength() reads the Content-Length header from an incoming request without applying an upper bound. The parsed value, a usize, is subsequently added to another offset inside wsRecv() without an overflow-safe operation. In Zig Debug and ReleaseSafe builds, integer overflow triggers a runtime panic, which terminates the hosting x64dbg process along with any attached debugging session.
Because this parsing occurs before the MCP token authentication check, no credentials are required to reach the vulnerable code path. The overflowed value is used only in a size comparison, so the impact is restricted to denial of service. There is no path to memory corruption or arbitrary code execution.
Root Cause
The root cause is an unbounded header value combined with unchecked arithmetic. parseContentLength() does not clamp or validate the attacker-controlled integer, and the downstream wsRecv() logic uses standard + addition rather than Zig's overflow-aware helpers such as @addWithOverflow or saturating arithmetic.
Attack Vector
An attacker with network reachability to the plugin's HTTP listener sends a single POST request containing a near-maximum Content-Length value. The default 0.0.0.0 bind in affected versions exposes the service on all interfaces, widening the attack surface to any routable network. No session, token, or user interaction is needed.
// Patch excerpt - src/core/config.zig (v1.2)
pub fn load() Config {
const default_port: u16 = if (@sizeOf(usize) == 8) 9094 else 9095;
var cfg = Config{ .port = default_port };
- const default_ip = "0.0.0.0";
+ const default_ip = "127.0.0.1";
@memcpy(cfg.ip[0..default_ip.len], default_ip);
cfg.ip_len = default_ip.len;
// Source: https://github.com/duty1g/x64dbg-mcp-server/commit/0dd4204d37c81d8b605133dc48c14886eeac1562
The patch changes the default bind address to the loopback interface, eliminating remote exposure for default installations. The companion change in src/core/mcp_server.zig bumps SERVER_VERSION to 1.2 and corrects the arithmetic in the request-handling path.
Detection Methods for CVE-2026-107820
Indicators of Compromise
- Unexpected termination of the x64dbg.exe process with a Zig runtime panic message referencing integer overflow.
- Inbound HTTP requests to the MCP listener (default TCP ports 9094 or 9095) containing abnormally large Content-Length header values.
- Loss of an active debugging session shortly after an untrusted connection to the plugin's HTTP endpoint.
Detection Strategies
- Inspect HTTP traffic to x64dbg-MCP endpoints and flag Content-Length values approaching usize boundaries, such as values near 2^64 - 1.
- Correlate x64dbg process crashes with recent network connections to ports 9094 or 9095 from non-loopback addresses.
- Review installed plugin versions and alert when x64dbg-mcp-server reports a SERVER_VERSION lower than 1.2.
Monitoring Recommendations
- Enable network telemetry on developer and reverse-engineering workstations where x64dbg is installed.
- Log all bind addresses used by debugger plugins and alert on any non-loopback listener.
- Capture process crash dumps for x64dbg.exe and route them to a central log store for triage.
How to Mitigate CVE-2026-107820
Immediate Actions Required
- Upgrade x64dbg-mcp-server to version 1.2 or later as published in the GitHub Release v1.2.
- Restrict the plugin's HTTP listener to the loopback interface by setting the bind address to 127.0.0.1.
- Block inbound traffic to ports 9094 and 9095 at the host firewall on analyst workstations.
Patch Information
The fix is delivered in version 1.2 through commit 0dd4204. The patch changes the default bind address from 0.0.0.0 to 127.0.0.1 and corrects the arithmetic path that previously allowed the panic. Additional context is available in the GitHub Security Advisory GHSA-4478-h5jv-647m and GHSA-jgj3-97w2-9v9r.
Workarounds
- Manually edit the plugin configuration to bind the HTTP listener to 127.0.0.1 instead of 0.0.0.0.
- Run x64dbg only on isolated analysis networks when the plugin must remain network-reachable.
- Terminate or unload the MCP plugin when it is not actively required for AI-assisted debugging sessions.
# Verify x64dbg-mcp-server is bound only to the loopback interface
netstat -ano | findstr /R ":9094 :9095"
# Expected output should show 127.0.0.1:9094 or 127.0.0.1:9095, not 0.0.0.0
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

