CVE-2026-1579
The MAVLink communication protocol does not require cryptographic authentication by default.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.93%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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 4.0
- 9.3 CRITICALCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.93% probability · 58th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-306
- Affected
- px4/autopilot
- Source
- ics-cert@hq.dhs.gov
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-090-02.jsonThird Party Advisory
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-090-02Third Party Advisory, US Government Resource
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.