/

CVE-2026-81735

Severity:

CRITICAL RISK

(10.0)

Missing Authentication (CWE-306) in UI-TARS MCP Server

CVE-2026-81735

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Remote Code Execution and File Access

Severity:

CRITICAL RISK

(10.0)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CVE-2026-81735 is a critical missing-authentication vulnerability in the UI-TARS-desktop MCP HTTP server. When deployed with the affected defaults, network-reachable MCP endpoints may expose command execution and filesystem tools without requiring credentials, allowing an attacker to run commands or read and modify files as the server process.

Affected context

The vulnerability occurs in deployments using the mcp-http-server package's Streamable HTTP or SSE transports when no authentication middleware is supplied. The vulnerable entry points start the commands and filesystem servers with host and port parameters only, while the server may bind to every network interface when no host is specified. Exposure depends on network reachability, deployment configuration, and the privileges of the process running the server.

Exploit preconditions

  • Attack surface: Streamable HTTP and SSE MCP endpoints exposed over a reachable network socket
  • Required access: Network connectivity to the listening port; no credential is required when middleware is omitted
  • Trigger point: Invocation of exposed command or filesystem MCP tools
  • Why exploitation is possible: Authentication is optional, and the affected entry points do not provide middleware while the server may listen on all interfaces
  • Privilege boundary: Actions occur with the operating-system permissions of the server process

Why this happens

The underlying defect is an insecure authentication design in which authorization middleware is applied only when a caller explicitly provides it. The affected server entry points omit that middleware, leaving sensitive tools available without an identity check. The default listen address of :: further broadens exposure by binding the service to every interface. This behavior maps to CWE-306: Missing Authentication for Critical Function, because security-sensitive operations can be reached without verifying the caller.

Potential impact

  • An unauthenticated attacker may execute arbitrary commands as the server process
  • Attackers could read, create, modify, or delete files accessible to that process
  • Sensitive credentials, source code, and configuration data may be exposed
  • The host or surrounding environment could be compromised through available operating-system privileges
  • Compromised systems could be used for persistence, lateral movement, or data destruction

General mitigation guidance

Mitigation generally focuses on making authentication and authorization mandatory for any network-exposed MCP transport.

Common defensive patterns include:

  • Require authentication middleware by default and fail closed when it is absent
  • Bind services to localhost or another explicitly intended interface unless broader exposure is necessary
  • Place externally reachable services behind a trusted access-control boundary
  • Apply per-tool authorization so command execution and filesystem operations are separately controlled
  • Run the server under a dedicated least-privilege account with restricted filesystem and process permissions
  • Prefer narrowly scoped tools and disable high-impact capabilities when they are not required
  • Protect configuration and deployment controls that determine host, port, and middleware behavior

How teams detect issues like this

Detection can combine source review, deployment inspection, and runtime monitoring:

  • Use static analysis to flag network servers that make authentication middleware optional or invoke sensitive handlers without an authorization check
  • Review calls to server-start functions and verify that every production entry point supplies authentication and authorization controls
  • Search deployment configuration for wildcard listen addresses and externally reachable MCP ports
  • Enforce policy checks requiring authentication for services exposing command execution or filesystem tools
  • Monitor MCP requests, child-process creation, and unusual file access by the server identity
  • Use automated code review tools to identify missing authentication, unsafe defaults, and excessive process privileges

Sources

SourceLink
github.comgithub.com/bytedance/UI-TARS-desktop
github.comgithub.com/bytedance/UI-TARS-desktop/blob/e9f3387288da4af2ad99972da2ac916cdabce093/packages/agent-infra/mcp-http-server/src/startServer.ts#L263
github.comgithub.com/bytedance/UI-TARS-desktop/commit/c2ad42e3eb9b27830db41a3e6f51ca7179d9b168
github.comgithub.com/bytedance/UI-TARS-desktop/pull/1918
vulncheck.comvulncheck.com/advisories/ui-tars-desktop-agent-infra-mcp-servers-bind-every-interface-without-authentication-exposing-arbitrary-command-execution

Frequently asked

questions

Yes, when an affected MCP endpoint is reachable by an attacker and the server is running without effective authentication middleware. Exploitability is limited by network controls and the interfaces on which the service listens.

The attacker generally needs network access to the exposed Streamable HTTP or SSE port. No application credential is required when the affected entry points omit authentication middleware.

Require authentication and authorization by default, bind the service only to intended interfaces, and restrict command and filesystem tools according to least privilege.

Treat authentication as a mandatory server invariant, fail closed when security middleware is missing, review all network exposure settings, and enforce CI or deployment policies for sensitive tool endpoints.

Find out what's already
exploitable in your codebase.