CVE
DJI AeroScope Mobile signature bypass in firmware update process
Only affects the 1300 communications board firmware of DJI AeroScope Mobile (TP703) from 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
DJI AeroScope Mobile (TP703) and its 1300 communications board firmware accept firmware updates without verifying a cryptographic signature, which lets an attacker on the same local network, without logging in, install modified firmware and gain persistent code execution as root. The attacker reaches the board over the network through TCP port 16000, and the attack works only when the unit is not connected to another controlling host.
Read the original description
Improper verification of cryptographic signature (CWE-347) in the firmware update handler 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 install modified firmware, which gives persistent code execution as root. The device accepts any image that matches an MD5 checksum supplied in the same request and does not verify a signature. Exploitation requires network access to TCP port 16000 on the board and that the unit is not connected to another controlling host. Reproduced by running the unmodified device binaries in emulation; not tested 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.
Who should check
Operators of DJI AeroScope Mobile (TP703) units with 1300 communications board firmware that are reachable on TCP 16000 and not controlled by another host
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-128909 (DJI AeroScope Mobile: Firmware updates are not signature-verified), 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-128909 (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):
- Affects DJI AeroScope Mobile (TP703) with 1300 communications board (source: https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128909/)
- Attacker needs network access to TCP port 16000 on the board (source: https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128909/)
- Board must not be controlled by another host (source: https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-128909/)
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-128909)
CISA KEV: CVE-2026-128909 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128909 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-128909/
- https://www.dji.com/aeroscope
- https://github.com/llorencroma/dji-aeroscope-root
- https://www.cve.org/CVERecord?id=CVE-2026-128909
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-128909
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-128909"}.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-128909
Is CVE-2026-128909 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?
Firmware updates on the 1300 communications board are not checked for a valid signature, so modified firmware can be installed. The advisory says this can give persistent code execution as root.Source: cyber-defence-campus.github.io, cve.org
Which versions are affected by CVE-2026-128909?
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?
The affected firmware range is 02.00.07.12 through 02.00.08.40 on the 1300 communications board of the DJI AeroScope Mobile (TP703). The attack needs network access to TCP port 16000 on the board and only works while no other host is controlling the board. Compare the board's firmware version with that range.Source: cyber-defence-campus.github.io, cve.org
How do I fix CVE-2026-128909?
No fixed version or vendor patch is named, so there is no upgrade target yet. Until one is published, follow the advisory's 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: 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. Do not route or bridge that segment to other networks.Source: cyber-defence-campus.github.io, cve.org