VulnerabilityPublished 2 Feb 2026Updated 23 Feb 2026

CVE-2026-1743: DJI Mavic Mini · Authentication Bypass by Capture-replay

Affects DJI Mavic MiniSource CVE Database V5

Public exploit available · CVSS 2.3 Low.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Adjacent
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
DJIMavic Mini	Affected =01.00	Fixed in–
DJIAir	Affected =01.00	Fixed in–
DJISpark	Affected =01.00	Fixed in–
DJIMini SE	Affected =01.00	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement strict network segmentation and access controls to prevent unauthorized devices from joining local networks where DJI drones operate. Use dedicated, isolated Wi-Fi networks for drone operations to minimize exposure. Monitor network traffic for unusual capture-replay patterns or repeated authentication attempts. Employ physical security measures to restrict proximity access to drones and their controllers. Until DJI releases a firmware update addressing this issue, avoid using affected firmware versions in sensitive environments. Consider disabling Enhanced Wi-Fi Pairing if possible or using alternative secure pairing methods. Regularly audit drone firmware versions and update promptly once patches become available. Additionally, educate drone operators about the risks of connecting to untrusted networks and the importance of operational security.

Description

A vulnerability has been found in DJI Mavic Mini, Air, Spark and Mini SE up to 01.00.0500. Affected by this vulnerability is an unknown functionality of the component Enhanced Wi-Fi Pairing. The manipulation leads to authentication bypass by capture-replay. The attack must be carried out from within the local network. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of this vulnerability is unauthorized access to the drone's pairing process, which could lead to control or data interception during the Wi-Fi pairing phase. For organizations relying on DJI drones for critical operations such as surveying, inspection, or security, this could result in operational disruption or leakage of sensitive information. However, the requirement for local network access and the high complexity of the attack significantly limit the scope and likelihood of exploitation. The absence of known exploits in the wild further reduces immediate risk. Nonetheless, in environments where adversaries can gain local network access—such as corporate campuses, event venues, or restricted areas—this vulnerability could be leveraged to bypass authentication controls. The lack of vendor response and patches means the risk remains unmitigated, potentially exposing users to future attacks as exploit techniques evolve. Overall, the impact is low but non-negligible for high-security contexts.

Summary

CVE-2026-1743 identifies a security vulnerability in DJI drones including the Mavic Mini, Air, Spark, and Mini SE models running firmware up to version 01.00.0500. The vulnerability resides in the Enhanced Wi-Fi Pairing feature, which is responsible for establishing secure connections between the drone and its controller or other devices. The flaw allows an attacker to perform an authentication bypass through a capture-replay attack, where previously captured authentication data packets are replayed to gain unauthorized access. This attack requires the adversary to be present on the same local network as the drone, such as a shared Wi-Fi environment. The complexity of the attack is high due to the need to capture and accurately replay packets without triggering security mechanisms, and no user interaction or privileges are necessary. The vendor DJI was notified early but has not issued any patches or official response. The vulnerability has been publicly disclosed, increasing the risk of potential exploitation despite the current lack of known active exploits. The CVSS 4.0 base score is 2.3, indicating low severity primarily due to the attack complexity, limited attack vector (local network only), and minimal impact on confidentiality, integrity, and availability. This vulnerability could allow unauthorized control or data access on affected drones if exploited, potentially compromising drone operations or sensitive data transmitted during pairing.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:56 UTC

Technical details

References

Community reviews

Related threats