Skip to main content
VulnerabilityPublished Updated

CVE-2026-32706: PX4-Autopilot · Classic Buffer Overflow

Affects PX4-AutopilotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.17.0-rc2 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade PX4-Autopilot to 1.17.0-rc2.

Affected software

ProductAffectedFixed in
PX4PX4-AutopilotAffected
  • <1.17.0-rc2
Fixed in
  • 1.17.0-rc2
GitHubpx4/PX4-Autopilotpkg:github/px4/PX4-AutopilotOther threatsAffected
  • =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

  1. Upgrade PX4-Autopilot to version 1.17.0-rc2 or later, where the vulnerability is patched with proper bounds checking.
  2. Restrict access to the CRSF serial port by implementing physical security controls to prevent unauthorized proximity or connection.
  3. If possible, disable the crsf_rc parser or CRSF protocol on serial ports that do not require it to reduce the attack surface.
  4. Employ network segmentation and access controls to isolate drone control interfaces from untrusted networks or users.
  5. Monitor drone system logs and behavior for anomalies that could indicate exploitation attempts or crashes.
  6. Conduct regular security audits of drone firmware versions and configurations to ensure compliance with updated security standards.
  7. For deployments with remote or wireless CRSF interfaces, consider additional encryption or authentication layers to prevent unauthorized packet injection.
  8. Train operators and maintenance personnel on the importance of firmware updates and physical security around drone control hardware.

Description

PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc2, The crsf_rc parser accepts an oversized variable-length known packet and copies it into a fixed 64-byte global buffer without a bounds check. In deployments where crsf_rc is enabled on a CRSF serial port, an adjacent/raw-serial attacker can trigger memory corruption and crash PX4. This vulnerability is fixed in 1.17.0-rc2.

References

Community reviews

Loading reviews…