9.8
CRITICAL CVSS 3.1
CVE-2026-1579
PX4 Autopilot Missing authentication for critical function
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.

INFO

Published Date :

March 31, 2026, 9:16 p.m.

Last Modified :

March 31, 2026, 9:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-1579 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 CRITICAL 7d14cffa-0d7d-4270-9dc0-52cabd5a23a6
CVSS 3.1 CRITICAL [email protected]
CVSS 4.0 CRITICAL 7d14cffa-0d7d-4270-9dc0-52cabd5a23a6
CVSS 4.0 CRITICAL [email protected]
Solution
Enable MAVLink 2.0 message signing for cryptographic authentication.
  • Enable MAVLink 2.0 message signing.
  • Configure cryptographic authentication for MAVLink.
  • Reject unsigned MAVLink messages at protocol level.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-1579 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-1579 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-1579 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Mar. 31, 2026

    Action Type Old Value New Value
    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.
    Added CVSS V4.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/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    Added CWE CWE-306
    Added Reference https://docs.px4.io/main/en/mavlink/message_signing
    Added Reference https://docs.px4.io/main/en/mavlink/security_hardening
    Added Reference https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-090-02.json
    Added Reference https://www.cisa.gov/news-events/ics-advisories/icsa-26-090-02
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.