# CVE-2026-107824: x64dbg-MCP Server exposes debugger operations to unauthenticated network clients

> Unauthenticated network clients can execute arbitrary debugger commands and access memory via the x64dbg-MCP Server's default HTTP interface.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 14 Oct 2026

## What is CVE-2026-107824?

CVE-2026-107824 is a critical missing authorization vulnerability in duty1g x64dbg-mcp-server, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-107824?


## How do I fix CVE-2026-107824?

No fix has been published for CVE-2026-107824 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107824 being exploited?

There is no known exploitation of CVE-2026-107824 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107824 and fix it if it is affected.

What it is: CVE-2026-107824 is a critical missing authorization vulnerability in duty1g x64dbg-mcp-server, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107824 in the wild and no public exploit code.

Affected product: duty1g x64dbg-mcp-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107824/ (Markdown: https://insights.sbomify.com/CVE-2026-107824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107824
- OSV: https://osv.dev/vulnerability/CVE-2026-107824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107824/
Summaries are generated and may contain mistakes; the official description above is the record.