Description
Microsoft UFO is an open-source framework for intelligent automation across devices and platforms. Prior to 3.0.10, the type_text and launch_app tools in ufo/client/mcp/http_servers/mobile_mcp_server.py pass the authenticated caller-controlled text and package_name parameters into adb shell command argument positions without comprehensive validation. The adb client joins those arguments into a remote command string that the Android shell reparses, allowing shell metacharacters to execute additional commands on an authorized connected device as the Android shell user. Exploitation requires a valid Mobile MCP API key and a reachable device authorized for ADB, and it does not establish host operating-system execution, Android root execution, or access beyond the Android shell-user privileges. This issue is fixed in version 3.0.10.
References5
- github.com/microsoft/UFO/commit/214443218bf4a3b8de798fd44e7fd77…
- github.com/microsoft/UFO/commit/a538791043327a0c33731d5be428867…
- github.com/microsoft/UFO/releases/tag/v3.0.10
- github.com/microsoft/UFO/security/advisories/GHSA-6ppj-5886-4f26
- github.com/microsoft/UFO/security/advisories/GHSA-6ppj-5886-4f26
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 65 · as of 10 November 2026
- CWE
- CWE-78CWE-88
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.