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.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
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
Workaround
No workaround given by the vendor.
Wed, 01 Apr 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PX4 Autopilot Missing authentication for critical function | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: icscert
Published:
Updated: 2026-03-31T20:36:09.044Z
Reserved: 2026-01-28T22:27:22.970Z
Link: CVE-2026-1579
Updated: 2026-03-31T20:36:03.968Z
Status : Received
Published: 2026-03-31T21:16:27.897
Modified: 2026-03-31T21:16:27.897
Link: CVE-2026-1579
No data.
OpenCVE Enrichment
No data.