CVE-2026-1579 PUBLISHED

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.

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

Message signing configuration documentation can be found at  https://docs.px4.io/main/en/mavlink/message_signing

• Dolev Aviv of Cyviation reported this vulnerability to CISA. finder

• https://docs.px4.io/main/en/mavlink/security_hardening
• https://docs.px4.io/main/en/mavlink/message_signing
• https://www.cisa.gov/news-events/ics-advisories/icsa-26-090-02
• https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-090-02.json

• CWE-306 CWE