Critical severity · published Mar 31, 2026
CVE-2026-1579
PX4 Autopilot Missing authentication for critical function
9.8
CVSS
0.9%
EPSS
No
On KEV
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 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 60% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
AU
Autopilot · PX4
v1.16.0 SITL · source: vendor, NVD
In the news
VulnerabilityCritical
PX4 Autopilot
View CSAF
Summary
Successful exploitation of this vulnerability could allow an attacker with access to the MAVLink interface to execute arbitrary shell commands without cryptographic authentication.
The following versions of PX4 Autopilot are affected:
Autopilot v1.16.0_SITL_latest_stable (CVE-2026-1579)
CVSS
Vendor
Equipment
Vulnerabilities
v3 9.8
PX4
PX4 Autopilot
Missing Authentication for Critical Function
Background
Critical Infrastructure Sectors: Transportation Systems, Emergency Services, Defense Industrial Base
Countries/Areas Deployed: Worldwide
Company Headquarters Location: Switzerland
Vulnerabilities
Expand All +
CVE-2026-1579
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.
View CVE Details
Affected Products
PX4 Autopilot
Vendor: PX4
Product Version: PX4 Autopilot: v1.16.0_SITL_latest_stable
Product Status: known_affected
Remediations
Mitigation PX4 recommends enabling MAVLink 2.0 message sign...
Mar 31, 2026·CISA Advisories
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-1579
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-1579
Product
https://docs.px4.io/main/en/mavlink/message_signing
Product
https://docs.px4.io/main/en/mavlink/security_hardening
Third Party Advisory
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
