CVE-2026-128910 · Infrastructure
NO FIX YET
The 1300 communications board in DJI AeroScope Mobile ships with the same hard-coded root password hash on every unit, stored as DES crypt. An attacker with physical access to the board's serial console can log in as root, and recover the password offline from the public firmware.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only units of the DJI AeroScope Mobile (TP703) with the affected firmware are exposed, and only to someone who can open the board and reach its serial console. The sources say DJI has discontinued the product and no fixed firmware exists, so the fix is to retire or isolate the unit. Networked use with default settings is not reported as exploitable.
Not affected if no-physical-access, other-firmware-versions, serial-console-locked
Who cares aeroscope, dji, drone-detection, embedded
02.00.07.12 through 02.00.08.40, and the AeroScope Mobile (TP703) firmware against 03.00.00.26.No fix yet, per the sources.
Use of hard-coded credentials (CWE-798) on 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 attacker with physical access to the board's serial console to log in as root. The same password hash is present on every unit and uses DES crypt, so the password can be recovered offline from the distributed firmware. No network login service accepts this password by default. 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.
This page as .md · .json · CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.