CVE-2026-107824: x64dbg-MCP Server exposes debugger operations to unauthenticated network clients
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
x64dbg-MCP Serverto a version that resolves this vulnerability.Fixed in 1.1
Event History
Frequently Asked Questions
Which deployments are exposed to unauthenticated access?
Versions prior to 1.1 are exposed when the service is reachable over the network. The server listens on 0.0.0.0 by default, exposing port 9094 for x64 and port 9095 for x32.
What does an attacker need to exploit this issue?
An attacker only needs network access to the server's default listening port. No authentication is required.
What actions can an unauthenticated client perform?
A reachable client can execute arbitrary x64dbg commands, attach to processes by PID, read and write debuggee memory, and write files to arbitrary paths.
What should be done if the server cannot be upgraded immediately?
Restrict network reachability to the service ports so unauthenticated clients cannot connect. The vulnerable default configuration listens on all interfaces.
How can I determine whether an instance is affected?
An instance is affected if it runs a version prior to 1.1 and exposes its HTTP/SSE service to clients that can reach port 9094 for x64 or 9095 for x32.