CVE-2026-32709: PX4 Autopilot MAVLink FTP Unauthenticated Path Traversal (Arbitrary File Read/Write/Delete)
PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc2, An unauthenticated path traversal vulnerability in the PX4 Autopilot MAVLink FTP implementation allows any MAVLink peer to read, write, create, delete, and rename arbitrary files on the flight controller filesystem without authentication. On NuttX targets, the FTP root directory is an empty string, meaning attacker-supplied paths are passed directly to filesystem syscalls with no prefix or sanitization for read operations. On POSIX targets (Linux companion computers, SITL), the write-path validation function unconditionally returns true, providing no protection. A TOCTOU race condition in the write validation on NuttX further allows bypassing the only existing guard. This vulnerability is fixed in 1.17.0-rc2.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32709?
CVE-2026-32709 has been classified with a critical severity level due to its potential for unauthorized file access and manipulation.
How do I fix CVE-2026-32709?
To remediate CVE-2026-32709, upgrade to PX4 Autopilot version 1.17.0-rc2 or later as it addresses the unauthenticated path traversal vulnerability.
What vulnerabilities are associated with CVE-2026-32709?
CVE-2026-32709 allows unauthenticated users to exploit the MAVLink FTP implementation, enabling arbitrary file read, write, and delete operations.
Who is affected by CVE-2026-32709?
Users of PX4 Autopilot versions prior to 1.17.0-rc2 are vulnerable to CVE-2026-32709.
What is the impact of CVE-2026-32709?
The impact of CVE-2026-32709 includes potential unauthorized access to sensitive files and the ability to modify or delete critical files within the PX4 Autopilot system.