AdvisoriesToolsStatsChecklistSubmitGet the email
← All advisories
CVE-2026-107824criticalCode execution2026-10-09

CVE-2026-107824: x64dbg-MCP Server gave anyone on the network full debugger control

Early versions of the x64dbg-MCP Server plugin served all 71 debugger tools over HTTP/SSE with no authentication on 0.0.0.0, so anyone who could reach port 9094 or 9095 could run x64dbg commands, attach to processes, edit memory and write files.

01.

What it is

The plugin exposes x64dbg's debugging API to MCP clients. Out of the box it listened on every interface (port 9094 for x64, 9095 for x32) with no credential check.

The project's advisory lists arbitrary x64dbg command execution, attaching to any process by PID, reading and patching debuggee memory, and writing files to any path through the dump commands.

The fix adds a mandatory Bearer token that's generated on first run; requests without it get 401.

02.

How to check

  1. The GitHub advisory lists versions before 1.0 as affected and 1.0 as fixed; the NVD record says the fix is in 1.1.
  2. A separate, medium-severity bug (CVE-2026-107820, a pre-auth denial of service via Content-Length) affects 1.1 and earlier.
03.

How to fix

  1. Upgrade the plugin to 1.2 or later, which covers both advisories.
  2. Keep the MCP port bound to localhost or firewalled, especially on analysis machines.
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.