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.
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.
How to check
- 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.
- A separate, medium-severity bug (CVE-2026-107820, a pre-auth denial of service via Content-Length) affects 1.1 and earlier.
How to fix
- Upgrade the plugin to 1.2 or later, which covers both advisories.
- Keep the MCP port bound to localhost or firewalled, especially on analysis machines.
Sources
More advisories for this tool
- criticalCVE-2026-102503: Google Agent Mesh let any peer call MCP backends through an unchecked ingress
- criticalCVE-2026-96620: Claude Agent SDK (Python) resume option lets attackers run commands
- criticalCVE-2026-95182: DeepSeek Harness can be tricked into running a planted fake npx
- criticalCVE-2026-77366: obsidian-tc MCP server let any token read and edit any vault