Overview

CVE-2026-105793 is a critical vulnerability in Microsoft UFO, an open-source framework for intelligent automation across devices and platforms. The vulnerability has a CVSS score of 9.1 and is classified as CWE-78. It affects versions of UFO prior to 3.0.9. Understanding this vulnerability is crucial for security practitioners and technical learners to defend against potential attacks.

Understanding the Vulnerability / Threat

Root Cause Analysis

The root cause of CVE-2026-105793 is a design issue in the `press_key` tool in `ufo/client/mcp/http_servers/mobile_mcp_server.py`. The tool accepts a free-form `key_code` parameter and passes it to `adb shell input keyevent`. The `adb` client joins the arguments into a remote command string that the Android shell reparses, allowing an authenticated Mobile MCP caller to execute additional commands as the Android shell user on an authorized connected device.

Attack Surface & Vector

The vulnerability lives in the `mobile_mcp_server.py` file of the UFO framework. An attacker can reach this vulnerability through a network-adjacent or remote unauthenticated attack vector. The preconditions needed for exploitation include a valid `UFO_MCP_API_KEY`, `adb` on the host, and a reachable authorized device.

Exploitation Mechanics — Scenario Walkthrough

Scenario: Compromising a Corporate UFO Instance 1. Initial Position: An attacker gains access to a corporate network with a valid `UFO_MCP_API_KEY` and knowledge of the UFO framework's configuration. 2. Triggering the Flaw: The attacker crafts a malicious request to the `mobile_mcp_server.py` file, passing a specially crafted `key_code` parameter that is not properly sanitized. 3. What Breaks: The `adb` client joins the arguments into a remote command string that the Android shell reparses, allowing the attacker to execute additional commands as the Android shell user on an authorized connected device. 4. Attacker's Prize: The attacker gains the ability to execute commands as the Android shell user, potentially leading to lateral movement, data exfiltration, or persistence.

Real-World Impact

The real-world impact of CVE-2026-105793 is significant, as it allows an authenticated attacker to execute additional commands as the Android shell user on a connected device. This could lead to data theft, lateral movement, or ransomware deployment. Although there is no evidence of active exploitation in the wild, the vulnerability's high CVSS score and potential impact make it a critical concern for organizations using UFO.

Detection & Defense

Immediate Mitigations

To mitigate CVE-2026-105793, organizations should upgrade to UFO version 3.0.9 or later. Additionally, they should ensure that `adb` is properly configured and secured on the host system.

Detection Strategies

Defenders can detect exploitation attempts by monitoring log patterns, such as unusual `adb` activity or suspicious requests to the `mobile_mcp_server.py` file. They can also implement SIEM rules or network signatures to detect potential attacks.

Long-Term Hardening

To prevent this class of vulnerability, organizations should implement defense-in-depth strategies, such as:
  • Properly sanitizing user input
  • Implementing secure coding practices
  • Regularly updating and patching software
  • Conducting thorough security testing and vulnerability assessments

Key Takeaways

* CVE-2026-105793 is a critical vulnerability in Microsoft UFO that allows an authenticated attacker to execute additional commands as the Android shell user on a connected device. * The vulnerability is caused by a design issue in the `press_key` tool and can be mitigated by upgrading to UFO version 3.0.9 or later. * Defenders should implement detection strategies, such as monitoring log patterns and implementing SIEM rules, to detect potential attacks. * Organizations should prioritize defense-in-depth strategies to prevent this class of vulnerability.

Sources

* National Vulnerability Database (NVD) * Microsoft UFO security advisory