# CVE-2026-128910: DJI AeroScope Mobile: Hard-coded root password on the serial console


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-ghhg-w6h4-w3rm

## What is CVE-2026-128910?

CVE-2026-128910 is a medium-severity vulnerability in DJI AeroScope Mobile (TP703), published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2026-128910?


## How do I fix CVE-2026-128910?

No fix has been published for CVE-2026-128910 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-128910 being exploited?

There is no known exploitation of CVE-2026-128910 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128910 and fix it if it is affected.

What it is: CVE-2026-128910 is a medium-severity vulnerability in DJI AeroScope Mobile (TP703), published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128910 in the wild and no public exploit code.

Affected product: DJI AeroScope Mobile (TP703). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128910/ (Markdown: https://insights.sbomify.com/CVE-2026-128910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128910
- OSV: https://osv.dev/vulnerability/CVE-2026-128910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128910/
Summaries are generated and may contain mistakes; the official description above is the record.
