Critical Microsoft Teams Flaw CVE-2023-29324 Lets Attackers Control Android Devices

Key Takeaways

• A critical vulnerability, CVE-2026-73296, affects Microsoft’s open-source UFO automation framework.
• The flaw allows unauthenticated remote attackers to view and fully control connected Android devices and emulators.
• Affected versions are UFO releases prior to 3.0.8, particularly when Mobile Model Context Protocol (MCP) services are exposed for remote access.
• The vulnerability carries a CVSS score of 9.4 (Critical) and requires no user interaction or prior authentication to exploit.
• Microsoft has released UFO version 3.0.8 to patch the issue, implementing mandatory bearer token authentication.

Critical Microsoft UFO Flaw Exposes Android Devices to Remote Takeover

A severe security vulnerability within Microsoft’s open-source UFO automation framework, identified as CVE-2026-73296, presents a critical risk, potentially allowing remote attackers to gain unauthorized viewing and control capabilities over Android devices. This flaw, which boasts a CVSS score of 9.4 out of 10, enables malicious actors to operate compromised devices without needing any authentication or user interaction.

The vulnerability impacts Microsoft UFO versions preceding 3.0.8, specifically when the Mobile Model Context Protocol (MCP) services are configured for remote accessibility. Microsoft has since released UFO version 3.0.8 to mitigate this significant security loophole. The UFO framework incorporates Mobile MCP servers designed for data collection from and automation of Android devices linked via the Android Debug Bridge (ADB).

Technical Details of the Vulnerability

These critical services can be exposed over HTTP for remote operations. The data-collection server, which is vulnerable, operates on TCP port 8020, while the action server utilizes TCP port 8021. When administrators follow the project’s recommended remote deployment model and bind these services to 0.0.0.0, any system capable of reaching these ports could potentially leverage the Android automation functions.

Researchers discovered that the Mobile MCP servers failed to enforce authentication protocols before processing MCP requests. This critical oversight meant that an attacker could initiate a session and execute sensitive commands without providing any valid credentials. The vulnerability resides within the mobile_mcp_server.py component, specifically within the functions responsible for creating the Mobile data-collection and action servers.

According to the GitHub Advisory GHSA-24fq-m9rr-g3mm, the vulnerability is classified under CWE-306 (Missing Authentication for Critical Function) and CWE-862 (Missing Authorization).

Impact of Exploitation

An exposed Mobile MCP data server can provide attackers with a wealth of sensitive information, including screenshots, UI hierarchy data, details of installed applications, window-control information, and Android device metadata. This level of access could expose highly confidential data visible on a connected phone or emulator, such as chat conversations, email content, one-time passwords, account credentials, business application data, and authentication prompts.

The action server poses an even greater threat due to its exposure of ADB-backed control features. An unauthenticated attacker could remotely perform actions like tapping arbitrary screen locations, swiping, typing text, triggering Android key events, launching applications, and interacting with user interface controls. Essentially, an attacker could interact with an unlocked, connected device in the same manner as an legitimate automation workflow. The full extent of impact depends on the device’s current state, active applications, and the permissions granted to the ADB process. However, this flaw unequivocally enables unauthorized modifications and disruption of normal device operations.

Mitigation and Remediation

The default UFO configuration binds the Mobile MCP services to localhost, which inherently limits network exposure in untouched installations. The vulnerability becomes particularly dangerous when operators intentionally expose these services via a non-loopback address for remote deployment purposes. The attack vector is network-based, low-complexity, and requires no prior privileges, existing UFO login, browser interaction, or API key to exploit a vulnerable, network-exposed deployment.

The immediate remediation is to upgrade to UFO version 3.0.8 or later. This updated release introduces mandatory bearer token authentication for the Mobile MCP servers, utilizing the UFO_MCP_API_KEY environment variable for credential management. The revised implementation is designed to prevent startup if the required API key is absent.

What You Should Do

• Upgrade Immediately: Update all Microsoft UFO installations to version 3.0.8 or newer to apply the critical security patch.
• Restrict Network Access: Until all systems are updated, ensure that Mobile MCP services are restricted to localhost.
• Block Ports: Block inbound access to TCP ports 8020 and 8021 on network firewalls. Avoid direct exposure of these ports to the internet.
• Secure Remote Deployments: For necessary remote deployments, implement TLS encryption and use an authenticated reverse proxy or a trusted private tunnel.
• Identify and Review: Security teams should identify all hosts running UFO, review connected ADB devices and emulators, and rotate any credentials that might have been exposed on screens.
• Investigate Anomalies: Be vigilant for unusual automation activity, including unexpected screen taps, text entry, application launches, or screenshots, which could indicate compromise.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.