Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Px4 | Autopilot | 1.16.0 |
Related Weaknesses (CWE)
References
- https://docs.px4.io/main/en/mavlink/message_signingProduct
- https://docs.px4.io/main/en/mavlink/security_hardeningProduct
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-09Third Party Advisory
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-090-02Third Party AdvisoryUS Government Resource
FAQ
What is CVE-2026-1579?
CVE-2026-1579 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 ...
How severe is CVE-2026-1579?
CVE-2026-1579 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-1579?
Check the references section above for vendor advisories and patch information. Affected products include: Px4 Autopilot.