CVE-2026-78255: DJI Drone HTTP Media Server Allows Unauthenticated Access to Stored Media
The HTTP media server running on DJI drones serves stored photos and videos through the /v2 endpoint without authenticating the requesting client. Filenames follow a predictable pattern, allowing an attacker who joins the drone's internal network to enumerate valid filenames and exfiltrate stored photos and videos. The exposed media may reveal sensitive information, including private locations, property, travel history, identifiable individuals, and the operator's routines.
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.
Affected Software
Event History
Frequently Asked Questions
Who can access the exposed media?
An attacker must join the drone's internal network. Once connected, the attacker can request stored photos and videos from the HTTP media server without authenticating.
How does an attacker find media to download?
Stored-media filenames follow a predictable pattern, allowing an attacker on the internal network to enumerate valid filenames and retrieve the corresponding files through the /v2 endpoint.
How can I determine whether a drone is affected?
Check the drone model and firmware version. The issue affects the listed models running firmware earlier than the corresponding version stated for that model, such as DJI Neo before 01.00.0400 and DJI Air 3 before 01.00.1600.