VulnerabilityPublished 13 Mar 2026Updated 17 Mar 2026

CVE-2026-32713: PX4-Autopilot · Always-Incorrect Control Flow Implementation

Affects PX4-AutopilotSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.17.0-rc2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.17.0-rc2

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

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

Attack Vector: Adjacent: The vulnerable component is bound to the network 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 physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Upgrade PX4-Autopilot to 1.17.0-rc2.

Affected software

Product	Affected	Fixed in
PX4PX4-Autopilot	Affected <1.17.0-rc2	Fixed in 1.17.0-rc2
GitHubpx4/PX4-Autopilot`pkg:github/px4/PX4-Autopilot`Other threats	Affected =1.17.0-rc2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32713, organizations should promptly upgrade PX4-Autopilot installations to version 1.17.0-rc2 or later, where the logic error in MAVLink FTP session validation is corrected. For environments where immediate patching is not feasible, consider disabling the MAVLink FTP service if it is not essential to drone operations, thereby eliminating the attack surface. Implement network-level controls such as firewall rules or segmentation to restrict access to the MAVLink FTP port, limiting exposure to untrusted networks. Monitoring and logging MAVLink FTP session activity can help detect anomalous or unauthorized operations indicative of exploitation attempts. Additionally, review and harden drone operational procedures to minimize reliance on FTP file transfers during critical missions. Vendors and integrators should verify that their PX4-based systems incorporate the patched version and communicate the importance of updates to end users. Finally, maintain awareness of PX4 security advisories and subscribe to relevant threat intelligence feeds for emerging exploit information.

Description

PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc2, A logic error in the PX4 Autopilot MAVLink FTP session validation uses incorrect boolean logic (&& instead of ||), allowing BurstReadFile and WriteFile operations to proceed with invalid sessions or closed file descriptors. This enables an unauthenticated attacker to put the FTP subsystem into an inconsistent state, trigger operations on invalid file descriptors, and bypass session isolation checks. This vulnerability is fixed in 1.17.0-rc2.

Impact

The primary impact of CVE-2026-32713 is on the availability and reliability of the PX4-Autopilot's FTP subsystem. By allowing unauthenticated attackers to bypass session validation, the vulnerability can cause the FTP service to enter an inconsistent state, potentially leading to crashes or denial of service conditions. This can disrupt drone operations that depend on PX4 for flight control and file transfer, affecting mission-critical tasks such as firmware updates, data logging, or configuration management. Although the vulnerability does not directly expose sensitive data or allow code execution, the loss of availability can have operational consequences, especially in commercial, industrial, or defense drone deployments. Organizations operating fleets of drones with PX4 versions prior to 1.17.0-rc2 may face increased risk of service interruptions or degraded performance. The lack of authentication requirements and user interaction lowers the barrier for exploitation, making remote attacks feasible. However, the scope is limited to the FTP subsystem and does not compromise the overall flight control system's integrity or confidentiality.

References

github.com/PX4/PX4-Autopilot/security/advisories/GHSA-pp2c-jr5g-6f2m (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 23:12 UTC

WeaknessesCWE-670

Technical details

References

Community reviews

Related threats