Skip to main content
VulnerabilityPublished

CVE-2026-1579: PX4 Autopilot · Missing Authentication

Affects PX4 AutopilotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PX4AutopilotAffected
  • =v1.16.0 SITL
Fixed in–

AI-suggested

To mitigate CVE-2026-1579, organizations should immediately enable MAVLink 2.0 message signing on all PX4 Autopilot systems to enforce cryptographic authentication of all MAVLink messages. This ensures that unsigned or tampered messages are rejected at the protocol level. Additionally, restrict access to the MAVLink interface by implementing network segmentation, firewall rules, and strong access controls to limit exposure to trusted entities only. Regularly update PX4 Autopilot software to the latest versions that may include security enhancements and patches. Employ monitoring and anomaly detection on MAVLink traffic to identify unauthorized message attempts. For deployments in sensitive environments, consider using encrypted communication channels (e.g., VPNs or secure tunnels) to protect MAVLink traffic from interception or injection. Conduct security audits and penetration testing focused on UAV communication interfaces. Finally, educate operators and administrators about the importance of enabling message signing and securing drone communication to prevent exploitation.

Description

The MAVLink communication protocol does not require cryptographic authentication by default. When MAVLink 2.0 message signing is not enabled, any message -- including SERIAL_CONTROL, which provides interactive shell access -- can be sent by an unauthenticated party with access to the MAVLink interface. PX4 provides MAVLink 2.0 message signing as the cryptographic authentication mechanism for all MAVLink communication. When signing is enabled, unsigned messages are rejected at the protocol level.

References

Community reviews

Loading reviews…