CVE-2026-1579
CriticalCVSS 9.8Exploitation Probability (EPSS)
Elevated risk57th percentile - higher than 57% of all known CVEs
Summary
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 providing interactive shell access, can be sent by an unauthenticated party with access to the MAVLink interface. PX4 provides message signing as the cryptographic authentication mechanism, and when enabled, unsigned messages are rejected at the protocol level.
Risk Assessment
Lack of required authentication allows an unauthenticated attacker to take control of the device by sending crafted MAVLink messages, potentially leading to full system compromise.
Recommendation
Enable MAVLink 2.0 message signing on all devices and systems using the MAVLink protocol to reject unauthenticated messages.
Original NVD description (English source)
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.