Skip to main content

CVE-2026-128908DJI AeroScope Mobile (TP703) OS command injection

Schedule itHigh8.8EPSS not scored yet

CVE-2026-128908 is a OS command injection in DJI AeroScope Mobile (TP703), rated high (8.8 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Input reaches an operating-system command line, letting an attacker run their own commands on the host.

How it is reached

An attacker can exploit it from the same local network segment, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place DJI AeroScope Mobile (TP703) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. Segment the networks that can reach it.

Description from NVD

OS command injection (CWE-78) in the network-configuration handling of the management service (uavmonitor_usbv1) of the 1300 communications board in DJI AeroScope Mobile (TP703) firmware 03.00.00.26, with 1300 communications board firmware 02.00.07.12 through 02.00.08.40, allows an unauthenticated attacker on the local network to execute arbitrary commands as root. Configuration values that can be written without authentication over the management interface are inserted unquoted into shell commands. Exploitation requires network access to TCP port 16000 on the board and that the unit is not connected to another controlling host. The injected command persists across reboots. Confirmed on a physical device.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer. DJI has discontinued AeroScope Mobile and no fixed firmware is available.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Network edge devices: VPNs, firewalls, routers and gateways. They sit between the internet and internal networks, so a flaw in one is often the first step into everything behind it.
  • Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
  • Template engines. The flaw sits between untrusted input and code or command execution.

Trust boundaries in play

  • Local network segment. The attacker must share a network segment with the target.
  • Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.

Questions to answer about your own systems

  • Where does DJI AeroScope Mobile (TP703) run in your systems, and at which version?
  • Which network segments can reach them?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.