cve.bz

CVE-2026-77812 dji: Missing Encryption of Sensitive Data

9.4 criticalEPSS 0.1%

Critical (9.4) in dji. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.4 critical
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
EPSS
0.1% (unchanged from 0.1% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-311 Missing Encryption of Sensitive Data
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-77812 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77812?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77812?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77812 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • dji:air 3
  • dji:air 3s
  • dji:avata 2
  • dji:avata 360
  • dji:dji flip
  • dji:mavic 3
  • dji:mavic 3 classic
  • dji:mavic 3 pro
  • dji:mavic 4 pro
  • dji:mini 2
  • dji:mini 3
  • dji:mini 3 pro
  • dji:mini 4 pro
  • dji:mini 5 pro
  • dji:neo
  • dji:neo 2

Versions

From the CNA's record in the CVE List.

ProductAffected
DJI Neothrough 01.00.0400
DJI Neo 2through 01.00.0500
DJI Flipthrough 01.00.1200
DJI Air 3through 01.00.1600
DJI Air 3Sthrough 01.00.1400
DJI Avata 2through 01.00.0400
DJI Avata 360through 01.00.0300
DJI Mavic 3through 01.00.1400
DJI Mavic 3 Classicthrough 01.00.0800
DJI Mavic 3 Prothrough 01.01.0700
DJI Mavic 4 Prothrough 01.00.0500
DJI Mini 2through 01.07.0200
DJI Mini 3through 01.00.0500
DJI Mini 3 Prothrough 01.00.0900
DJI Mini 4 Prothrough 01.00.1100
DJI Mini 5 Prothrough 01.00.0600

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Wh02m1/CVE-2026-77812 Harbor Check: matches CVE 7 stars, Python, created
    DJI Drone Cleartext Bluetooth Transmission of Wi-Fi PSK and Session UUID — Proof of Concept for CVE-2026-77812.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-311 (14).

References

Check your stackJSON