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…
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, 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 protoco…
In-depth triage · Auto channel
No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).
Affected products
- :
Lint boundary warnings (2)
The following non-blocking warnings were raised during the lint phase of this triage (e.g. reference URLs not yet on the allowlist). They do not affect entry usability and are disclosed for transparency (see DR-002).
-
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://docs.px4.io/main/en/mavlink/message_signing -
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://docs.px4.io/main/en/mavlink/security_hardening
Sources
- NVD DATABASE
Original Links
- https://docs.px4.io/main/en/mavlink/message_signing Product
- https://docs.px4.io/main/en/mavlink/security_hardening Product
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-090-02.json Third Party Advisory
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-090-02 Third Party Advisory
Timeline
- nvd_ingest NVD