Neo: Missing Encryption of Sensitive Data
CVE-2026-77812 is a critical-severity missing encryption of sensitive data vulnerability in Neo from DJI, with a CVSS 4.0 base score of 9.4 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Neo versions: 01.00.0400 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.12% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Neo you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| DJI | Neo | 01.00.0400 and earlier | Not stated |
| DJI | Neo 2 | 01.00.0500 and earlier | Not stated |
| DJI | DJI Flip | 01.00.1200 and earlier | Not stated |
| DJI | Air 3 | 01.00.1600 and earlier | Not stated |
| DJI | Air 3S | 01.00.1400 and earlier | Not stated |
| DJI | Avata 2 | 01.00.0400 and earlier | Not stated |
| DJI | Avata 360 | 01.00.0300 and earlier | Not stated |
| DJI | Mavic 3 | 01.00.1400 and earlier | Not stated |
| DJI | Mavic 3 Classic | 01.00.0800 and earlier | Not stated |
| DJI | Mavic 3 Pro | 01.01.0700 and earlier | Not stated |
| DJI | Mavic 4 Pro | 01.00.0500 and earlier | Not stated |
| DJI | Mini 2 | 01.07.0200 and earlier | Not stated |
| DJI | Mini 3 | 01.00.0500 and earlier | Not stated |
| DJI | Mini 3 Pro | 01.00.0900 and earlier | Not stated |
| DJI | Mini 4 Pro | 01.00.1100 and earlier | Not stated |
| DJI | Mini 5 Pro | 01.00.0600 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- HighSerious loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- HighSerious loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.
Official description
DJI drones transmit DUML (DJI Universal Markup Language) protocol messages over BLE (Bluetooth Low Energy) without encryption. When a client attempts to connect to the drone over Wi-Fi, or when the drone is switched to QuickTransfer mode, the DJI Fly application exchanges DUML messages with the drone over BLE, including the Wi-Fi credentials. An attacker within BLE range can passively sniff this traffic and recover the credentials in cleartext, including the drone's Wi-Fi PSK, SSID, and trusted identifier UUID. Obtaining these credentials allows the attacker to join the drone's internal Wi-Fi network, interact with network services exposed by the drone, and decrypt Wi-Fi traffic exchanged between the drone and the legitimate user. * An attacker within BLE range recovers the Wi-Fi SSID and PSK in cleartext, and can then join the drone's network * The same capture also exposes the session UUID identifier, which is the only thing the drone uses to tell a trusted client from an unknown one, so the attacker can replay it and skip the physical confirmation of new connected devices. * The credentials do not change between sessions unless the operator manually resets the Wi-Fi settings, so one capture stays valid indefinitely * The attack is fully passive, with nothing transmitted and no connection made, so neither the operator nor the drone has any indication the session was observed * A BLE sniffer and presence during one normal DJI Fly connection are needed 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. There is no user-side mitigation that fully addresses the vulnerability without upgrading.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Encryption of Sensitive Data
The product does not encrypt sensitive or critical information before storage or transmission.
How developers prevent this class of flaw
- Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
More Missing Encryption of Sensitive Data vulnerabilities (CWE-311)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Neo
- 9.3 Critical severity
- 8.5 High severity
- 8.7 High severity
Recent Missing Encryption of Sensitive Data vulnerabilities
- 9.8 Critical severity
- 7.4 High severity
- 7.5 High severity
- 7.5 High severity
- 9.6 Critical severity
- 9.4 Critical severity
Spotted an error? Tell us.