ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-1579

The MAVLink communication protocol does not require cryptographic authentication by default.

Published Mar 31, 2026 · catalog updated Jul 29, 2026 · The MAVLink communication protocol

Check if you run it

No confirmed exploitation is on record for CVE-2026-1579. EPSS is 0.93%. Act only if a listed version of The MAVLink communication protocol is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The MAVLink communication protocol).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.93%
Remediation
Advisory link
Affected products
cpe px4/autopilot

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe px4/autopilot1.16.0

How to fix CVE-2026-1579

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-1579. EPSS is 0.93%. Act only if a listed version of The MAVLink communication protocol is installed.

Which versions are affected?

Compare what you have installed with 1.16.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-306: Missing Authentication for Critical Function. EPSS 0.93%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 31, 2026 · NIST NVD

    Detected

    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 M

  2. Jul 29, 2026 · NIST NVD

    Updated

    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 M

Sources

  • CVE.orgVulnerability recordCVE-2026-1579

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-1579

    30-day exploitation probability 0.9%

    first.org
  • NIST NVDVulnerability recordCVE-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 acces

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.