Skip to main content
VulnerabilityPublished

CVE-2026-105788: microsoft UFO · OS Command Injection

Affects microsoft UFOSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 3.0.10 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade UFO and microsoft/UFO to 3.0.10.

Affected software

ProductAffectedFixed in
microsoftUFOAffected
  • <3.0.10
Fixed in
  • 3.0.10
GitHubmicrosoft/UFOpkg:github/microsoft/UFOOther threatsAffected
  • <3.0.10
Fixed in
  • 3.0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Microsoft UFO to version 3.0.10 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the improper input validation that leads to command injection.

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.

References

Community reviews

Loading reviews…