CVE-2026-107824

CriticalCVSS 9.3

Published: 09/10/2026(UTC)Translated: 10/10/2026(UTC)NVD NIST

Summary

In versions prior to 1.1, x64dbg-MCP Server (a native MCP plugin for x64dbg) exposes all MCP debugger tools over HTTP and SSE without authentication while listening on 0.0.0.0 by default. Any unauthenticated network client that can reach the default port (9094 for x64, 9095 for x32) can execute arbitrary x64dbg commands, attach to processes by PID, read and write debuggee memory, and write files to arbitrary paths. This issue is fixed in version 1.1.

Risk Assessment

An attacker on the network can gain full control over the debugger, potentially leading to process integrity compromise, data theft, or privilege escalation.

Recommendation

Update x64dbg-MCP Server to version 1.1 or later to require authentication and restrict listening to trusted interfaces.

Other vulnerabilities in x64dbg-MCP Server

CVE-2026-107820Medium
x64dbg-MCP Server before version 1.2 has an integer overflow vulnerability in parseContentLength() and wsRecv(), allowing an unauthenticated network client to trigger a panic and terminate the x64dbg process. The server listens on 0.0.0.0 by default, increasing attack surface. Fixed in version 1.2.

Original NVD description (English source)

x64dbg-MCP Server is a native Model Context Protocol (MCP) plugin for x64dbg that exposes the debugger's full functionality over HTTP. Prior to 1.1, x64dbg-MCP Server exposes all MCP debugger tools over HTTP and SSE without authentication while listening on 0.0.0.0 by default. Any unauthenticated network client that can reach the default port, 9094 for x64 or 9095 for x32, can execute arbitrary x64dbg commands, attach to processes by PID, read and write debuggee memory, and write files to arbitrary paths. This issue is fixed in version 1.1.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS