Summary
CVE-2026-73296 is a missing-authentication vulnerability in Microsoft’s UFO (UFO³) agent framework that allows an unauthenticated network attacker to remotely control and exfiltrate data from connected Android devices. The flaw resides in UFO’s Mobile MCP (Model Context Protocol) HTTP servers, which expose privileged device-automation tools on ports 8020 and 8021 without any credential check when deployed for remote access. The issue carries a CVSS v3.1 base score of 9.4 (Critical) and is tracked as GHSA-24fq-m9rr-g3mm.
Technical details
- Root cause: The Mobile MCP HTTP server implementation (
ufo/client/mcp/http_servers/mobile_mcp_server.py) does not require or validate any authentication token before executing MCP tool calls, despite being designed for remote/non-loopback deployment. - Trigger conditions: The vulnerability is exploitable when the Mobile MCP servers are configured for remote deployment (bound to a network-reachable interface) on the default ports 8020/8021, rather than restricted to localhost.
- Attack vector: Network-based, no authentication or user interaction required. An attacker with network access to the exposed ports can directly invoke MCP tools.
- Impact: Exposed, unauthenticated MCP tools include
capture_screenshot,get_ui_tree,tap,swipe,type_text,launch_app,press_key, andclick_control. This allows an attacker to disclose Android screenshots, UI hierarchy data, installed-application information, window/device metadata, and to remotely inject taps, swipes, text input, key events, app launches, and control clicks — effectively granting full remote control of the connected mobile device. - CWE classifications: CWE-306 (Missing Authentication for Critical Function) and CWE-862 (Missing Authorization).
Affected software
- Microsoft UFO (UFO³ "Weaving the Digital Agent Galaxy" framework) — all versions up to and including v3.0.7.
Severity
- CVSS v3.1 Base Score: 9.4 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Mitigation and recommended actions
- Immediate: Upgrade to UFO v3.0.8 or later, which introduces mandatory bearer-token authentication for the Mobile MCP servers via the
UFO_MCP_API_KEYenvironment variable (validated using constant-time comparison), and refuses to start without it. - If upgrading is not immediately possible:
- Do not expose the Mobile MCP servers (ports 8020/8021) to untrusted networks; restrict them to localhost/loopback interfaces only.
- If remote access is required, place the servers behind a reverse proxy or VPN/private tunnel with TLS termination and strong access controls, since the underlying bearer-token scheme does not itself encrypt traffic.
- Apply network-level restrictions (firewall rules, security groups) to limit inbound access to these ports to trusted, authenticated management hosts only.
- Monitor for unexpected MCP tool invocations or anomalous device-control activity as an indicator of exploitation attempts.

