Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition BLE sniffer near operator
-
DeliveryOperator initiates Wi-Fi/QuickTransfer connection
-
ExploitPassively capture unencrypted DUML frames
-
ExecutionRecover SSID, PSK, and trust UUID
-
PersistJoin drone's internal Wi-Fi network
-
ImpactReplay UUID and decrypt operator traffic
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V14 - Data Protection Encryption of sensitive data
|
| Exploitation Conditions | Exploitation requires the attacker to be within BLE range of the drone (or its controlling phone) at the moment the DJI Fly app performs a Wi-Fi connection or the drone is switched to QuickTransfer mode - that connection event is the exact trigger that causes the unencrypted DUML credential exchange over BLE. No authentication and no attacker-side interaction are needed (PR:N/UI:N), and the capture is entirely passive, so nothing is transmitted and neither drone nor operator sees any indication. Limiting factors: the Adjacent (AV:A/BLE) vector means physical proximity during a live session is mandatory, so this is a proximity/targeted attack, not remote; the exposure only occurs when the operator actually initiates a Wi-Fi/QuickTransfer connection; and the affected firmware must be below the fixed version for the specific model. A key aggravator is that captured credentials remain valid indefinitely unless the operator manually resets the drone's Wi-Fi settings. |
| Impact | This is a genuine high-priority issue rather than an inflated CVSS number: the CVSS 4.0 base is 9.4 (AV:A/AC:L/AT:N/PR:N/UI:N with high confidentiality, integrity, and availability impact on both the vulnerable and subsequent systems), and the attack is fully passive, low-complexity, and requires no authentication or user interaction from the attacker's side. The main risk-limiting factor is the AV:A (Adjacent) vector - the attacker must be within BLE range during an actual DJI Fly connection event - which constrains this to a proximity/targeted attack rather than internet-wide mass exploitation, consistent with the absence of any EPSS-scale worming potential. No EPSS score, POC, or KEV entry is provided, so there is no evidence of active exploitation; however, the durability of the leak (credentials persist across sessions until manually reset) and the total lack of detectability meaningfully raise real-world risk for anyone operating these drones in contested or public environments. Even a mid-sized commercial or public-safety drone operator should treat this as urgent because a single capture stays valid indefinitely. |
| Exploit ScenarioDerived | An attacker positions a commodity BLE sniffer within radio range of a DJI operator (for example, at a public flying field or event) and passively records the BLE traffic while the operator makes a normal DJI Fly connection or triggers QuickTransfer. From that single capture the attacker extracts the drone's Wi-Fi SSID, PSK, and trust UUID, then later joins the drone's internal network and replays the UUID to be treated as an already-trusted device - skipping the physical new-device confirmation - while also decrypting the operator's Wi-Fi traffic. No public exploit code is identified, but the attack requires only inexpensive hardware and proximity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 21, 2026
Cleartext exposure of Wi-Fi credentials in DJI consumer and prosumer drones lets an attacker within Bluetooth range recover the drone's Wi-Fi SSID, PSK, and trusted-client UUID by passively sniffing unencrypted DUML-over-BLE messages exchanged during a normal DJI Fly connection or QuickTransfer handoff. This affects a broad range of current DJI models (Neo, Flip, Air 3/3S, Avata 2/360, Mavic 3 family, Mavic 4 Pro, and Mini 2 through Mini 5 Pro) below specific firmware versions. Recovered credentials grant the attacker access to the drone's internal Wi-Fi network and the ability to decrypt the operator's Wi-Fi traffic; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
Vendor-released patch: update each affected drone to at or above its listed fixed firmware version (e.g., DJI Neo 01.00.0400, DJI Air 3 01.00.1600, DJI Mavic 3 Pro 01.01.0700, DJI Mavic 4 Pro 01.00.0500, DJI Mini 5 Pro 01.00.0600, and the corresponding versions for the other models) via the DJI Fly app or DJI Assistant, per the DJI advisory at https://support.dji.com/help/content?customId=en-us03400011149&spaceId=34&re=US&lang=en. The vendor states there is no user-side mitigation that fully resolves the issue without upgrading. As partial compensating controls before patching: perform Wi-Fi/QuickTransfer connections only in RF-controlled areas away from untrusted parties to reduce the chance of a BLE sniffer being in range; manually reset the drone's Wi-Fi settings after any suspected exposure to invalidate a previously captured PSK (trade-off: must reconfigure trusted devices); and minimize use of QuickTransfer mode, which triggers the credential exchange over BLE (trade-off: slower media offload). These controls reduce opportunity but do not close the underlying plaintext-transmission flaw.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 16 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-311 (Missing Encryption of Sensitive Data): DJI's proprietary DUML (DJI Universal Markup Language) control protocol is transmitted over Bluetooth Low Energy without any transport encryption. During Wi-Fi association or when the drone enters QuickTransfer mode, the DJI Fly mobile app negotiates the Wi-Fi link by sending the credentials (SSID, PSK) and a session/trust UUID inside these plaintext DUML frames. Because BLE advertising and data channels are observable by any nearby radio, and because the drone relies solely on the UUID - rather than a cryptographic handshake or physical pairing confirmation - to distinguish a trusted client, capturing one exchange yields everything needed to impersonate a legitimate device. The affected products are enumerated in the CPE set under vendor 'dji' (e.g., cpe:2.3:a:dji:dji_mavic_3_pro:*).
Know when Dji Neo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Adjacent BLE sniffing with no privileges or interaction (AV:A/AC:L/PR:N/UI:N); credential disclosure is C:H, network join enables I:H, and scope changes (S:C) as the leaked creds compromise the drone network beyond the BLE component.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
DescriptionCVE.org
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.
Executive ViewAI
DJI consumer and prosumer drones (Neo, Flip, Air 3/3S, Avata 2/360, Mavic 3 family, Mavic 4 Pro, and Mini 2-5 Pro) transmit Wi-Fi credentials in cleartext over Bluetooth, allowing attackers within range to capture network credentials and decrypt operator traffic. Organizations deploying these drones for operations, surveillance, or security purposes face immediate risk of unauthorized network access and operator communication interception. This CRITICAL vulnerability affects a broad installed base with no available remediation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) disable Wi-Fi on affected drones where not operationally critical; (2) operate drone networks on physically isolated network segments with strict Layer 2 controls; (3) restrict Bluetooth attack surface through controlled operator positioning and airspace boundaries; (4) implement continuous network monitoring and alerting on drone Wi-Fi networks; (5) mandate VPN encryption for any operator-controlled traffic routed through compromised drone networks; (6) enforce physical security perimeters during drone operations to limit unauthorized Bluetooth proximity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-63973
GHSA-gh7r-589j-33x7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB