SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-81735

CRITICAL · CVSS 10 EPSS 0.53% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-27 · Last synced 2026-09-15

CyberRota Analysis

AI-Generated

The vulnerability affects the mcp-http-server package in F5's UI-TARS-desktop, where the default listen address is set to '::', allowing unauthorized access to Streamable HTTP and SSE MCP transports without authentication. This oversight enables unauthenticated clients to execute arbitrary commands and access file read/write functionalities, posing a critical risk to system integrity. Organizations using affected F5 products should prioritize immediate remediation to mitigate potential exploitation.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-81735
Severity
CRITICAL
CVSS
10
EPSS
0.53%
F5

Original NVD Description

startServer.ts in the mcp-http-server package of UI-TARS-desktop defaulted its listen address to '::' when no host was given, so startSseAndStreamableHttpMcpServer bound the Streamable HTTP and SSE MCP transports to every interface, and its authentication middleware was optional: middlewares are applied only when a caller supplies them. The @agent-infra/mcp-server-commands and @agent-infra/mcp-server-filesystem entry points call startSseAndStreamableHttpMcpServer with a host and port alone and pass no middleware, so neither server required a credential. The commands server exposes a run_command tool that hands its caller-supplied command string to promisify(child_process.exec), so any unauthenticated client able to reach the port could run arbitrary commands as the user running the server, and the filesystem server exposed its file read and write tools on the same terms. The listen default became 127.0.0.1 in commit c2ad42e3eb9b27830db41a3e6f51ca7179d9b168; the package version stayed at 1.2.4 across that change, so the boundary is the commit rather than a release.