CVE-2026-77812 — Cleartext Exposure of DJI Drone Wi-Fi Credentials via BLE
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (DJI Air 3, DJI Air 3S, DJI Avata 2…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| DJI | Air 3 | ≤ 01.00.1600 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Air 3S | ≤ 01.00.1400 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Avata 2 | ≤ 01.00.0400 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Avata 360 | ≤ 01.00.0300 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Flip | ≤ 01.00.1200 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mavic 3 | ≤ 01.00.1400 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mavic 3 Classic | ≤ 01.00.0800 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mavic 3 Pro | ≤ 01.01.0700 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mavic 4 Pro | ≤ 01.00.0500 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mini 2 | ≤ 01.07.0200 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mini 3 | ≤ 01.00.0500 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mini 3 Pro | ≤ 01.00.0900 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mini 4 Pro | ≤ 01.00.1100 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Mini 5 Pro | ≤ 01.00.0600 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Neo | ≤ 01.00.0400 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DJI | Neo 2 | ≤ 01.00.0500 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.4 | CVSS 4.0 | Critical | — | — | 5a6e4751-2f3f-4070-9419-94fb35b644e8 via NIST National Vulnerability Database |
| 9.4 | CVSS 4.0 | Critical | — | — | CIRCL via CVE Program (cve.org) e CISA ADP |
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 (score shown at the top: 5a6e4751-2f3f-4070-9419-94fb35b644e8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.09%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Check TLS negotiations and unexpected certificates in the component’s traffic.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · dji/neo, dji/neo 2, dji/dji flip, dji/air 3, dji/air 3s, dji/avata 2, dji/avata 360, dji/mavic 3, dji/mavic 3 classic, d
- SSVC assessment updated
- Record published
- CVSS changed · 9.4
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-78251 DJI Drone FTP Service Allows Unrestricted Storage Consumption of the /blackbox Directory Aug 27, 2026
- High CVE-2026-78306 DJI Drone Bluetooth Interface Unauthenticated DUML Command Execution Aug 24, 2026
- Medium CVE-2026-78321 DJI Drone HTTP Media Server Denial of Service via Connection Pool Exhaustion Aug 24, 2026
- High CVE-2026-78255 DJI Drone HTTP Media Server Allows Unauthenticated Access to Stored Media Aug 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-77812 is "Cleartext Exposure of DJI Drone Wi-Fi Credentials via BLE", rated Critical. It affects Air 3 (DJI); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.4 describes technical severity. EPSS 0.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.