Unauthenticated Bluetooth DUML commands can take over Wi-Fi on DJI drones

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-78306?

CVE-2026-78306 is a vulnerability classified as Missing Authentication for Critical Functionality, affecting Neo (affected versions: ≤ 01.00.0400), Neo 2 (affected versions: ≤ 01.00.0500), Flip (affected versions: ≤ 01.00.1200), and 13 more products. This vulnerability is rated High, with a CVSS score of 8.5. Current sources do not report this vulnerability as exploited.

Overview

Original source data

DJI drones expose an unauthenticated DUML command interface over Bluetooth that allows an attacker within Bluetooth range to modify Wi-Fi configuration parameters, including the SSID, PSK, MAC address, regulatory country code, and wireless channel. An attacker can overwrite the Wi-Fi PSK with a known value and connect to the drone's internal Wi-Fi network, potentially gaining access to the flight control interface and issuing flight commands. Crafted DUML commands can also disable or restart the Wi-Fi and Bluetooth interfaces, disconnect Wi-Fi clients, or reset wireless configuration, resulting in a denial-of-service condition that can disrupt the operator's wireless control, video, and telemetry connections during flight. 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.

Affected products and scope

  • DJI Neo: affected from 0 through 01.00.0400, inclusive.
  • DJI Neo 2: affected from 0 through 01.00.0500, inclusive.
  • DJI Flip: affected from 0 through 01.00.1200, inclusive.
  • DJI Air 3: affected from 0 through 01.00.1600, inclusive.
  • DJI Air 3S: affected from 0 through 01.00.1400, inclusive.
  • DJI Avata 2: affected from 0 through 01.00.0400, inclusive.
  • DJI Avata 360: affected from 0 through 01.00.0300, inclusive.
  • DJI Mavic 3: affected from 0 through 01.00.1400, inclusive.
  • DJI Mavic 3 Classic: affected from 0 through 01.00.0800, inclusive.
  • DJI Mavic 3 Pro: affected from 0 through 01.01.0700, inclusive.
  • DJI Mavic 4 Pro: affected from 0 through 01.00.0500, inclusive.
  • DJI Mini 2: affected from 0 through 01.07.0200, inclusive.
  • DJI Mini 3: affected from 0 through 01.00.0500, inclusive.
  • DJI Mini 3 Pro: affected from 0 through 01.00.0900, inclusive.
  • DJI Mini 4 Pro: affected from 0 through 01.00.1100, inclusive.
  • DJI Mini 5 Pro: affected from 0 through 01.00.0600, inclusive.

The normalized record marks the default status as unaffected outside the listed affected ranges. No exact fixed release is supplied for any branch, so a specific version or separate branch should not be treated as verified fixed without DJI confirmation.

Technical details

The affected component is the drone's Bluetooth interface, which establishes Wi-Fi connectivity and exchanges credentials. The public technical description states that trusted-UUID checking is applied to three read commands, while other DUML commands do not receive the same authentication check, consistent with CWE-306. An attacker within Bluetooth range can submit crafted DUML commands without prior authentication; the record describes no required user interaction and low attack complexity. Depending on the command, the attacker can modify the SSID, PSK, MAC address, country code, or Wi-Fi channel, control the radios, disconnect clients, reset wireless configuration, or restart or power off the aircraft. Overwriting the PSK with a known value may allow connection to the internal Wi-Fi network and potentially reach the flight control interface, but the downstream services and exact implementation details are not established. The vendor-side fix mechanism beyond firmware remediation has not been disclosed.

Exploitability

  • Reachability: The attack is performed over Bluetooth from within radio range of the drone.
  • Authentication and interaction: The record describes an unauthenticated DUML interface with no required prior privileges or user interaction.
  • Complexity: The supplied attack properties describe low attack complexity.
  • Public exploit material: A public proof-of-concept repository is available and describes unauthorized DUML command transmission, including operation in flight under stated control conditions.
  • Observed abuse: The available evidence does not establish in-the-wild exploitation, a specific campaign, a named victim, or observed abuse.

Technical impact

The vulnerability permits unauthorized changes to the integrity of Wi-Fi configuration and the state of the Bluetooth and Wi-Fi interfaces. If the PSK is changed to a value known by the attacker, the attacker may connect to the drone's internal network and potentially reach the flight control interface, although the final level of control and downstream service conditions are not fully established. Stopping or restarting radios, disconnecting clients, or resetting configuration can interrupt control, video, and telemetry during flight. The established primary consequences are loss of integrity and availability for flight operations; the available evidence does not establish a specific data breach, crash, or physical incident.

Business impact

Successful exploitation can make unauthorized changes to the drone's wireless configuration, creating recovery work for SSIDs, PSKs, channels, or other radio parameters. Potential access to the flight control interface could permit unauthorized flight commands or unsafe aircraft behavior, but this is a possible consequence rather than evidence of a specific incident. Disabling or restarting the radios, disconnecting clients, or resetting configuration can interrupt operator control, video, and telemetry during flight, disrupting missions and increasing operational risk. The public proof of concept also describes reset operations that may affect configuration and data stored on the aircraft. The available evidence does not establish a specific data breach, victim, campaign, or physical incident.

Remediation

  1. Update firmware: Apply a firmware update through DJI's vendor-supported update process. This is the only confirmed remediation in the record.
  2. Inventory by branch: Before flight, record the exact model and firmware version for each aircraft and compare it with the applicable affected boundary. Do not apply a fix for one model to another, and do not assume a later or parallel branch is fixed without DJI confirmation.
  3. Verify after updating: Confirm the installed version using official vendor tooling, then validate the SSID, PSK, MAC address, country code, Wi-Fi channel, and controller connectivity.
  4. Manage exposure while waiting: If an update cannot be applied, treat the listed versions as exposed and consider suspending high-consequence flights in environments where nearby Bluetooth access cannot be controlled. This is a precautionary measure, not a vendor-confirmed workaround.
  5. Investigate tampering: If unauthorized changes are found, do not resume flight solely because connectivity returns. Record the configuration, firmware version, and radio state for recovery and post-update verification.

Detection

  1. Inventory every DJI aircraft in the Neo, Flip, Air, Avata, Mavic, and Mini lines, recording the exact model and firmware version from vendor-supported management tooling.
  2. Compare each version with the affected boundaries in affected_summary. Do not treat the absence of an obvious anomaly or log entry as proof that the aircraft is safe.
  3. Review for unexpected changes to the SSID, PSK, MAC address, country code, or Wi-Fi channel, as well as unexpected Wi-Fi or Bluetooth radio stops, restarts, or client disconnections.
  4. Investigate loss of control, video, or telemetry connectivity during flight. These are operational symptoms requiring investigation, not confirmed standalone indicators of compromise.
  5. If unauthorized wireless changes are found, isolate the aircraft from high-consequence flight operations, preserve the model, version, and configuration information, and handle the device through DJI's firmware update process.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.