Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32708: CWE-121: Stack-based Buffer Overflow in PX4 PX4-Autopilot

0
High
VulnerabilityCVE-2026-32708cvecve-2026-32708cwe-121
Published: Fri Mar 13 2026 (03/13/2026, 21:18:53 UTC)
Source: CVE Database V5
Vendor/Project: PX4
Product: PX4-Autopilot

Description

PX4 autopilot is a flight control solution for drones. Prior to 1.17.0-rc2, the Zenoh uORB subscriber allocates a stack VLA directly from the incoming payload length without bounds. A remote Zenoh publisher can send an oversized fragmented message to force an unbounded stack allocation and copy, causing a stack overflow and crash of the Zenoh bridge task. This vulnerability is fixed in 1.17.0-rc2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/20/2026, 23:12:07 UTC

Technical Analysis

CVE-2026-32708 is a stack-based buffer overflow vulnerability identified in the PX4-Autopilot software, a widely used open-source flight control solution for drones. The vulnerability specifically resides in the Zenoh uORB subscriber module, which handles communication messages. Prior to version 1.17.0-rc2, this component allocates a variable-length array (VLA) on the stack directly based on the length of incoming payloads without enforcing any upper bounds. A remote Zenoh publisher can exploit this by sending an oversized fragmented message, causing the subscriber to allocate an excessively large stack buffer and copy data beyond the intended limits. This results in a stack overflow condition that crashes the Zenoh bridge task, potentially leading to denial of service and enabling further exploitation to compromise system confidentiality and integrity. The vulnerability requires low-level privileges (local access) but no user interaction, and the attack vector is local (AV:L). The CVSS v3.1 base score is 7.8, reflecting high severity due to the combined impact on confidentiality, integrity, and availability. The flaw was publicly disclosed on March 13, 2026, and has been addressed in PX4-Autopilot version 1.17.0-rc2. No known exploits in the wild have been reported to date.

Potential Impact

The vulnerability poses significant risks to organizations deploying PX4-Autopilot in drone operations, including commercial, industrial, and research applications. Exploitation can cause denial of service by crashing critical flight control components, potentially leading to loss of drone control and mission failure. Furthermore, the stack overflow may be leveraged to execute arbitrary code, compromising the confidentiality and integrity of the drone’s systems and data. This could enable attackers to manipulate flight behavior, intercept sensitive telemetry, or disrupt drone fleets. Given the increasing reliance on drones for logistics, surveillance, agriculture, and defense, such disruptions could have operational, financial, and safety consequences. The requirement for local access limits remote exploitation but insider threats or compromised local networks could facilitate attacks. The vulnerability’s presence in an open-source autopilot framework means that a broad range of drone manufacturers and operators using PX4-Autopilot versions prior to 1.17.0-rc2 are at risk.

Mitigation Recommendations

Organizations should immediately upgrade PX4-Autopilot to version 1.17.0-rc2 or later, where the vulnerability is fixed. Until upgrades are applied, restrict access to the Zenoh communication interface to trusted and authenticated entities only, minimizing exposure to untrusted local users or devices. Implement network segmentation and strict access controls to prevent unauthorized local access to drone control systems. Conduct thorough code reviews and fuzz testing on any custom extensions or integrations with the Zenoh uORB subscriber to detect similar unsafe memory operations. Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) where supported by the platform to mitigate exploitation impact. Monitor drone system logs for unusual crashes or communication anomalies indicative of attempted exploitation. Finally, maintain an incident response plan tailored to drone operational environments to quickly address potential compromises.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-13T14:33:42.824Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b485502f860ef943b833e7

Added to database: 3/13/2026, 9:44:48 PM

Last enriched: 3/20/2026, 11:12:07 PM

Last updated: 4/28/2026, 6:56:17 AM

Views: 130

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses