On this page
Atomicorp WAF Research Note: CVE-2026-81735
UI-TARS-desktop @agent-infra MCP Servers Bind Every Interface Without Authentication, Exposing Arbitrary Command Executi
CVE Details
- Already protected by existing Atomicorp WAF rules
- Protection status: Understanding Atomicorp WAF Protection Status
- CVE: CVE-2026-81735
- Name: UI-TARS-desktop @agent-infra MCP Servers Bind Every Interface Without Authentication, Exposing Arbitrary Command Executi
- Severity: Critical
- CVSS: 10.0 (v4.0) (Critical)
- CVSS version: 4.0
- CVSS source: VulnCheck CNA
- CVSS vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Attack vector: Network
- Attack complexity: Low
- Attack requirements: None
- Privileges required: None
- User interaction: None
- Vulnerable-system confidentiality: High
- Vulnerable-system integrity: High
- Vulnerable-system availability: High
- Subsequent-system confidentiality: High
- Subsequent-system integrity: High
- Subsequent-system availability: High
- Scope: X
- CWE: CWE-306 — Missing Authentication for Critical Function
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-12 (opens in a new tab) , CAPEC-166 (opens in a new tab) , CAPEC-216 (opens in a new tab) , CAPEC-36 (opens in a new tab) , CAPEC-62 (opens in a new tab)
- Vendor: bytedance
- Vulnerable product: UI-TARS-desktop
- CVE published: 2026-08-27
- CVE last modified: 2026-08-31
- EPSS: 0.0053; 43.4th percentile (FIRST (opens in a new tab) )
- Latest Update: 2026-09-06
- Selected Rule IDs observed: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 390904 , 393655
- Matching rules: 11; rules with blocking actions: 11
- Would-block Rule IDs: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 390904 , 393655
- Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data
Vulnerability 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.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 390904 , 393655 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Versions reported unaffected: bytedance UI-TARS-desktop version c2ad42e3eb9b27830db41a3e6f51ca7179d9b168.
- Affected versions: bytedance UI-TARS-desktop versions earlier than c2ad42e3eb9b27830db41a3e6f51ca7179d9b168.
- Recommended upgrade: Upgrade bytedance UI-TARS-desktop to c2ad42e3eb9b27830db41a3e6f51ca7179d9b168 or later.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://github.com/bytedance/UI-TARS-desktop (opens in a new tab)
- CVE authority reference: https://github.com/bytedance/UI-TARS-desktop/blob/e9f3387288da4af2ad99972da2ac916cdabce093/packages/agent-infra/mcp-http-server/src/startServer.ts#L263 (opens in a new tab)
- CVE authority reference: https://github.com/bytedance/UI-TARS-desktop/commit/c2ad42e3eb9b27830db41a3e6f51ca7179d9b168 (opens in a new tab)
- CVE authority reference: https://github.com/bytedance/UI-TARS-desktop/pull/1918 (opens in a new tab)
- CVE authority reference: https://www.vulncheck.com/advisories/ui-tars-desktop-agent-infra-mcp-servers-bind-every-interface-without-authentication-exposing-arbitrary-command-execution (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, rce, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .