CVE
DJI AeroScope Mobile root command injection in TCP configuration handler
Affects DJI AeroScope Mobile (TP703) 1300 communications board firmware 02.00.07.12 through 02.00.08.40. No fixed firmware is available.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: Connect the management Ethernet port only to an isolated network segment with no untrusted hosts, and do not route or bridge that segment to other networks.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Affected products are DJI AeroScope Mobile (TP703) and its 1300 communications board firmware. An attacker on the same local network, without logging in, can run arbitrary commands as root by sending unauthenticated configuration values over TCP port 16000 to a unit that is not connected to another controlling host, and the injected command survives reboots.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: Connect the management Ethernet port only to an isolated network segment with no untrusted hosts, and do not route or bridge that segment to other networks.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128908 (DJI AeroScope Mobile: OS command injection leads to root code execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128908 (entry last updated 2026-11-13):
Affected:
- DJI AeroScope Mobile (TP703): versions 03.00.00.26
- DJI AeroScope Mobile (TP703) 1300 communications board firmware: from 02.00.07.12, through 02.00.08.40
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Network access to TCP port 16000 on the board (source: https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128908/)
- The unit is not connected to another controlling host (source: https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128908/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
Workaround: Connect the management Ethernet port only to an isolated network segment with no untrusted hosts, and do not route or bridge that segment to other networks. (source: https://www.cve.org/CVERecord?id=CVE-2026-128908)
CISA KEV: CVE-2026-128908 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128908 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128908/
- https://www.dji.com/aeroscope
- https://github.com/llorencroma/dji-aeroscope-root
- https://www.cve.org/CVERecord?id=CVE-2026-128908
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128908
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128908"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- DJI AeroScope Mobile (TP703)
03.00.00.26
- DJI AeroScope Mobile (TP703) 1300 communications board firmware
From 02.00.07.12 · through 02.00.08.40
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128908
Is CVE-2026-128908 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An OS command injection flaw lets a network-reachable attacker run arbitrary commands as root on the board, and the injected command persists across reboots.Source: cyber-defence-campus.github.io, cve.org
Which versions are affected by CVE-2026-128908?
AeroScope Mobile (TP703): version 03.00.00.26. AeroScope Mobile (TP703) 1300 communications board firmware: from 02.00.07.12 through 02.00.08.40.Source: cve.now feed data
Am I affected, and how do I check?
Firmware of the 1300 communications board in AeroScope Mobile (TP703) from 02.00.07.12 through 02.00.08.40 is listed as affected. The issue needs network access to TCP port 16000 on the board and applies only while no other host is controlling the board; check the board's firmware version and whether that port is reachable from the network.Source: cyber-defence-campus.github.io, cve.org
How do I fix CVE-2026-128908?
The advisory names no fixed firmware version and no vendor patch IDs, so there is no upgrade target yet. Apply the workaround below until a fix is released.Source: cyber-defence-campus.github.io, cve.org
What if there's no patch?
Connect the management Ethernet port only to an isolated network segment with no untrusted hosts, and do not route or bridge that segment to other networks.Source: cyber-defence-campus.github.io, cve.org