CVE intelligence and bounded remediation

CVE-2026-32709 — PX4 autopilot is a flight control solution for drones

Medium CVSS 6.8

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.

Severity
Medium
CVSS
6.8 (3.1)
Published
2026-03-16
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-22

Affected products

  • dronecode / px4_drone_autopilot
  • dronecode / px4_drone_autopilot / 1.17.0

Showing 2 representative product identities from 4 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Path traversal, unsafe upload, and file handling

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace untrusted filenames, archive entries, URLs, and path segments into read, write, include, extraction, and upload operations.
  • Identify filesystem roots, mount permissions, symbolic-link behavior, archive handling, and whether uploaded content is web-accessible or executable.
  • Review canonicalization and containment checks across supported operating systems and storage backends.

Remediate safely

  • Generate server-side storage identifiers and resolve paths beneath a fixed root using filesystem-aware containment checks.
  • Reject absolute, parent-relative, alternate-separator, device, link, and archive entries that escape the intended root.
  • Store uploads outside executable or served paths, validate type and size, and use private atomic temporary files.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.