Critical Authentication Bypass in PX4 Autopilot MAVLink Protocol
Summary
CISA ICS-CERT published advisory ICSA-26-090-02 disclosing CVE-2026-1579, a critical vulnerability (CVSS 9.8) in PX4 Autopilot v1.16.0 affecting the MAVLink communication protocol. The flaw allows unauthenticated remote attackers to execute arbitrary shell commands via the MAVLink interface when message signing is not enabled. CISA and the vendor recommend enabling MAVLink 2.0 message signing on all non-USB communication links as the primary remediation.
What changed
CISA disclosed CVE-2026-1579, a critical vulnerability in PX4 Autopilot where the MAVLink protocol lacks cryptographic authentication by default. When MAVLink 2.0 message signing is not enabled, any party with access to the MAVLink interface can send messages including SERIALCONTROL, which provides interactive shell access. This affects PX4 Autopilot v1.16.0SITLlateststable. The vulnerability has a CVSS score of 9.8 and maps to CWE-306 (Missing Authentication for Critical Function). The vendor has published security hardening and message signing documentation as the recommended fix.
Organizations using affected PX4 Autopilot systems should immediately verify whether MAVLink 2.0 message signing is enabled on all non-USB communication links. If not enabled, configure message signing following the published documentation at docs.px4.io. CISA recommends minimizing network exposure of control system devices, isolating industrial control networks behind firewalls, and using secure remote access methods such as VPNs when required. Defense Industrial Base, transportation, and emergency services operators with PX4 deployments should prioritize this assessment given the critical infrastructure implications.
What to do next
- Identify all PX4 Autopilot deployments and verify MAVLink 2.0 message signing status
- Enable MAVLink 2.0 message signing on all non-USB communication links per vendor documentation
- Minimize network exposure and isolate affected systems from untrusted networks
Source document (simplified)
ICS Advisory
PX4 Autopilot
Release Date
March 31, 2026
Alert Code ICSA-26-090-02 Related topics: Industrial Control System Vulnerabilities, Industrial Control Systems View CSAF
Summary
Successful exploitation of this vulnerability could allow an attacker with access to the MAVLink interface to execute arbitrary shell commands without cryptographic authentication.
The following versions of PX4 Autopilot are affected:
- Autopilot v1.16.0SITLlatest_stable (CVE-2026-1579)
| CVSS | Vendor | Equipment | Vulnerabilities |
| --- | --- | --- | --- |
| v3 9.8 | PX4 | PX4 Autopilot | Missing Authentication for Critical Function |
Background
- Critical Infrastructure Sectors: Transportation Systems, Emergency Services, Defense Industrial Base
- Countries/Areas Deployed: Worldwide
- Company Headquarters Location: Switzerland
Vulnerabilities
CVE-2026-1579
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.
Affected Products
PX4 Autopilot
Vendor:
PX4 Product Version:
PX4 Autopilot: v1.16.0SITLlateststable Product Status:
knownaffected
Remediations
Mitigation
PX4 recommends enabling MAVLink 2.0 message signing as the authentication mechanism for all non‑USB communication links. PX4 has published a security hardening guide for integrators and manufacturers at https://docs.px4.io/main/en/mavlink/security_hardening.
https://docs.px4.io/main/en/mavlink/security_hardening
Mitigation
Message signing configuration documentation can be found at https://docs.px4.io/main/en/mavlink/message_signing.
https://docs.px4.io/main/en/mavlink/message_signing
Relevant CWE: CWE-306 Missing Authentication for Critical Function
Metrics
| CVSS Version | Base Score | Base Severity | Vector String |
| --- | --- | --- | --- |
| 3.1 | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Acknowledgments
- Dolev Aviv of Cyviation reported this vulnerability to CISA
Legal Notice and Terms of Use
This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).
Recommended Practices
CISA recommends users take defensive measures to minimize the risk of exploitation of this vulnerability.
Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the Internet.
Locate control system networks and remote devices behind firewalls and isolating them from business networks.
When remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices.
CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.
CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets.
Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.
Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.
CISA also recommends users take the following measures to protect themselves from social engineering attacks:
Do not click web links or open attachments in unsolicited email messages.
Refer to Recognizing and Avoiding Email Scams for more information on avoiding email scams.
Refer to Avoiding Social Engineering and Phishing Attacks for more information on social engineering attacks.
No known public exploitation specifically targeting this vulnerability has been reported to CISA at this time.
Revision History
- Initial Release Date: 2026-03-31
| Date | Revision | Summary |
| --- | --- | --- |
| 2026-03-31 | 1 | Initial Publication |
Legal Notice and Terms of Use
This product is provided subject to this Notification and this Privacy & Use policy.
Tags
Sector: Defense Industrial Base Sector, Emergency Services Sector, Transportation Systems Sector Topics: Industrial Control System Vulnerabilities, Industrial Control Systems
Please share your thoughts
We recently updated our anonymous product survey; we welcome your feedback.
Related Advisories
Mar 31, 2026
ICS Advisory | ICSA-26-090-01
Anritsu Remote Spectrum Monitor
Mar 26, 2026
ICS Advisory | ICSA-26-085-02
OpenCode Systems OC Messaging and USSD Gateway
Mar 26, 2026
ICS Advisory | ICSA-26-085-03
PTC Windchill Product Lifecycle Management
Mar 26, 2026
ICS Advisory | ICSA-26-085-01
WAGO GmbH & Co. KG Industrial Managed Switches
Named provisions
Related changes
Source
Classification
Who this affects
Taxonomy
Browse Categories
Get Data Privacy & Cybersecurity alerts
Weekly digest. AI-summarized, no noise.
Free. Unsubscribe anytime.
Get alerts for this source
We'll email you when CISA ICS-CERT Advisories publishes new changes.