Severity:

CRITICAL RISK

(9.8)

Missing Authentication / Inadequate Access Control

CVE-2026-1579

Analyzed

Vulnerability type

Category:

Missing Authentication / Inadequate Access Control

CWE:

CWE-306

Impact:

Remote Unauthorized Control and Potential System Takeover

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MAVLink, the telemetry and control protocol used by PX4 and other UAV systems, does not require cryptographic authentication by default.

When MAVLink 2.0 message signing is not enabled, any party with access to the MAVLink interface can inject control messages—including SERIAL_CONTROL that can expose interactive shell access—potentially resulting in full remote compromise of the vehicle or ground station.

Affected context

This weakness affects deployments where MAVLink communication is exposed over radio links, serial ports, or network transports without enabling MAVLink 2.0 message signing.

It is most relevant in scenarios where:

  • Flight controllers, companion computers, or ground-control stations accept MAVLink messages from interfaces that are physically or wirelessly reachable by untrusted parties.
  • Network-level protections (e.g., link encryption, VLAN isolation) are absent or misconfigured.
  • Operational procedures assume "whoever can speak MAVLink" is implicitly trusted.

In such contexts, attackers may be able to send arbitrary MAVLink messages to the system without any protocol-level authentication or integrity validation.

Exploit preconditions

  • Attack surface: Any MAVLink interface (e.g., telemetry radio, Wi-Fi/UDP, serial ports exposed via USB/UART, or bridged network endpoints).
  • Required access: Ability to transmit MAVLink-formatted traffic onto the same communication channel or physical link as the target system (e.g., being in RF range of a telemetry modem, plugged into an exposed serial port, or on the same IP network).
  • Trigger point: Processing of unauthenticated MAVLink packets when MAVLink 2.0 signing is not enabled or not enforced on the receiving endpoint.
  • Why exploitation is possible: The protocol, when used without signing, does not authenticate senders or verify message integrity. As a result, the receiver cannot distinguish legitimate traffic from spoofed or injected messages, allowing an unauthenticated actor to send privileged messages like SERIAL_CONTROL.

Why this happens

The underlying issue is a design-level reliance on optional authentication in a security-sensitive control channel.

MAVLink without signing implicitly trusts any incoming message, applying it to critical control and management interfaces without verifying the identity of the sender or the integrity of the content.

This maps to CWE-306: Missing Authentication for Critical Function, as operations that can influence flight behavior, system configuration, or shell access are not protected by mandatory authentication at the protocol level.

The insecure pattern is an unauthenticated command-and-control interface where cryptographic protections are available but not required or enforced by default, leading system integrators to deploy in an insecure configuration.

Potential impact

  • An attacker may send arbitrary control commands to a UAV, potentially altering flight paths or overriding operator inputs.
  • An attacker may use SERIAL_CONTROL or similar messages to gain interactive shell access to connected systems (e.g., flight controller console or companion computer).
  • An attacker could modify parameters, upload or alter mission plans, or change safety limits without authorization.
  • An attacker can disrupt or deny service by flooding or spoofing telemetry and command messages, causing confusion or loss of control.
  • An attacker may pivot from the flight controller to other connected components, increasing the blast radius of a compromise.

General mitigation guidance

Mitigation typically focuses on ensuring that MAVLink communication is authenticated and that trust in the transport is minimized.

Recommended defensive patterns include:

  • Enabling MAVLink 2.0 message signing for all control and telemetry links, and configuring endpoints to reject unsigned or improperly signed messages.
  • Treating all MAVLink links as untrusted by default and layering additional protections such as VPNs, link-layer encryption, or authenticated tunnels when possible.
  • Segregating control networks from general-purpose or public networks to reduce exposure of MAVLink interfaces.
  • Restricting which message types are accepted on specific interfaces, applying least-privilege principles to control channels.
  • Implementing operational policies requiring cryptographic keys management, rotation, and revocation for MAVLink signing keys.

These patterns reduce the risk that a reachable interface can be used as an unauthenticated control path into critical systems.

How teams detect issues like this

Detection and assurance approaches generally involve a mix of configuration validation, protocol monitoring, and code/architecture review:

  • Configuration validation: Regularly audit PX4 and ground-control configurations to verify that MAVLink 2.0 signing is enabled on all relevant endpoints and that unsigned messages are rejected.
  • Network and RF monitoring: Use protocol-aware monitoring (e.g., MAVLink decoders) to flag unsigned control messages on production links or to detect anomalous message sources or frequencies.
  • Architecture review: Assess system designs for any MAVLink endpoints bridged to wider networks, and document where authentication is absent or optional.
  • Static/automated checks: Incorporate checks in deployment tooling or CI pipelines that fail builds or deployments when MAVLink signing is disabled for production profiles.
  • Policy enforcement: Adopt security policies that require cryptographic protections for all command-and-control channels, and periodically test adherence via red-team or penetration testing exercises.

Sources

SourceLink
docs.px4.iodocs.px4.io/main/en/mavlink/message_signing
docs.px4.iodocs.px4.io/main/en/mavlink/security_hardening
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-090-02.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-090-02

Frequently asked

questions

Yes. If a MAVLink link (e.g., telemetry radio, Wi-Fi/UDP, or network bridge) is reachable by an attacker and MAVLink signing is not enforced, the attacker can send unauthenticated messages that the system will process as if they were legitimate.

It depends on the deployment. Physical access to a serial port or RF proximity to a telemetry link may be sufficient; no logical authentication is required at the protocol level when signing is disabled. If MAVLink is bridged onto an IP network, being on the same network segment can be enough.

The most robust pattern is to enable MAVLink 2.0 message signing on all control and telemetry endpoints and configure systems to reject unsigned traffic. This should be combined with network segmentation and, where possible, additional encryption or tunneling to protect confidentiality and integrity.

Future designs should treat command-and-control protocols as security-critical by default, requiring cryptographic authentication and integrity verification on all control messages. System integrators should enforce secure defaults, minimize exposed control interfaces, and incorporate security reviews and configuration checks into deployment and maintenance processes.

Find out what's already
exploitable in your codebase.