CVE-2026-1579: PX4 Autopilot Missing authentication for critical function

Published Mar 31, 2026
·
Updated

The MAVLink communication protocol does not require cryptographic authentication by default. When MAVLink 2.0 message signing is not enabled, any message -- including SERIALCONTROL, 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.

Affected Software

2 affected components
PX4 PX4 autopilot
PX4 Autopilot=1.16.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enable MAVLink 2.0 message signing in PX4 to provide cryptographic authentication for all non-USB communication links; when signing is enabled, unsigned MAVLink messages are rejected (including on interfaces such as the MAVLink interface that allow SERIAL_CONTROL/interactive shell-related functions).

    PX4 MAVLink 2.0 message signing MAVLink 2.0 message signing = enabled
  2. Compensating control

    Limit network/access to the PX4 MAVLink interface (non-USB communication links) so unauthenticated parties cannot send MAVLink messages when MAVLink 2.0 message signing is not enabled.

Event History

Mar 31, 2026
CVE Published
via MITRE·08:20 PM
Data Sourced
via MITRE·08:20 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-1579?

CVE-2026-1579 has a high severity due to the lack of cryptographic authentication in MAVLink communications, allowing unauthorized access.

2

How do I fix CVE-2026-1579?

To fix CVE-2026-1579, enable MAVLink 2.0 message signing and configure the system to require cryptographic authentication.

3

What systems are affected by CVE-2026-1579?

CVE-2026-1579 affects the PX4 Autopilot system which uses the MAVLink communication protocol.

4

What can attackers do with CVE-2026-1579?

Attackers can exploit CVE-2026-1579 to send unauthorized MAVLink messages, potentially gaining interactive shell access.

5

Is CVE-2026-1579 publicly known?

Yes, CVE-2026-1579 is a publicly reported vulnerability, highlighting its critical nature and the need for immediate attention.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203