CVE-2026-73296: Microsoft UFO: Unauthenticated Mobile MCP access allows remote Android device control and screen disclosure
Microsoft UFO open-source framework for intelligent automation across devices and platforms. Prior to 3.0.8, create_mobile_data_collection_server and create_mobile_action_server in ufo/client/mcp/http_servers/mobile_mcp_server.py exposed Streamable HTTP MCP services on TCP ports 8020 and 8021 without authentication, allowing an unauthenticated remote attacker to invoke capture_screenshot, get_ui_tree, tap, swipe, type_text, launch_app, press_key, and click_control against an ADB-connected Android device, disclose screen and device data, and modify device state. This issue is fixed in version 3.0.8.
Security readout for executives and security teams
Plain-English summary
Microsoft UFO versions before 3.0.8 can expose control of an ADB-connected Android device without requiring authentication. A network attacker reaching the affected services could view screenshots and device information, launch applications, enter text, and perform touch or key actions. This creates substantial confidentiality and integrity risk for connected devices.
Executive priority
Prioritize immediate remediation wherever affected services can be reached beyond a tightly controlled host or network. The weakness enables remote viewing and manipulation of connected Android devices without credentials. Isolate exposed services while teams upgrade, then review potentially reachable devices for sensitive screen content, applications, accounts, and unauthorized state changes.
Technical view
The mobile data-collection and action servers expose Streamable HTTP MCP services on TCP ports 8020 and 8021 without authentication. An unauthenticated network attacker can invoke screenshot, UI inspection, navigation, input, application-launch, and control functions against an ADB-connected Android device. The issue is classified as CWE-306 and CWE-862 and is fixed in UFO 3.0.8.
Likely exposure
Exposure requires Microsoft UFO earlier than 3.0.8, an affected mobile MCP server running, an ADB-connected Android device, and attacker network access to port 8020 or 8021. Internet-facing, shared-network, laboratory, CI, or automation environments may carry greater risk. The supplied sources do not quantify deployed exposure.
Exploitation context
The CVSS 3.1 score is 9.4, reflecting network access, low complexity, no privileges, and no user interaction. The supplied record does not identify confirmed exploitation, and the CVE is not listed as KEV in the provided bundle. Treat the vulnerability as readily actionable but do not claim active exploitation.
Researcher notes
The vulnerable functions are create_mobile_data_collection_server and create_mobile_action_server in ufo/client/mcp/http_servers/mobile_mcp_server.py. Impact includes screen and UI-tree disclosure plus device-state modification through exposed MCP capabilities. The provided sources establish the vulnerable versions and fix, but provide no evidence of exploitation prevalence or confirmed attacks.
Mitigation direction
Upgrade Microsoft UFO to version 3.0.8 or later.
Until upgraded, prevent untrusted network access to TCP ports 8020 and 8021.
Stop affected mobile MCP services when they are not required.
Restrict ADB-connected devices and review vendor guidance for additional safeguards.
Validation and detection
Inventory Microsoft UFO installations and confirm their installed versions.
Identify hosts running the mobile data-collection or action server functions.
Verify whether TCP ports 8020 or 8021 are reachable from untrusted networks.
Confirm connected Android devices and assess data or applications potentially exposed.
After upgrading, verify version 3.0.8 or later and retest network exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.