# CVE-2026-1743: DJI Mavic Mini/Air/Spark/Mini SE Enhanced Wi-Fi Pairing authentication replay

> Attackers on the local network can bypass authentication in DJI drone Wi-Fi pairing via replay attacks, requiring high complexity.

- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-f56m-qc2w-j8v5

## What is CVE-2026-1743?

CVE-2026-1743 is a low-severity authentication bypass vulnerability in DJI Air, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-294 (Authentication Bypass by Capture-replay), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-1743?


## How do I fix CVE-2026-1743?

No fix has been published for CVE-2026-1743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1743 being exploited?

There is no known exploitation of CVE-2026-1743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1743 and fix it if it is affected.

What it is: CVE-2026-1743 is a low-severity authentication bypass vulnerability in DJI Air, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1743 in the wild and no public exploit code.

Affected product: DJI Air. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1743/ (Markdown: https://insights.sbomify.com/CVE-2026-1743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1743
- OSV: https://osv.dev/vulnerability/CVE-2026-1743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1743/
Summaries are generated and may contain mistakes; the official description above is the record.