External risk intelligence

Ghost Robotics Vision 60 Unauthenticated Command Injection via MAVLink

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2025-41108

While the vulnerability affects remote communication via Wi-Fi or 4G/LTE, these robots are typically operated in localized environments or specialized field deployments. Public internet exposure is uncommon for this class of device, as they are not standard web-facing services or gateways, and communication is usually managed within private operational networks or direct control links.

Authentication Bypass

Ghostrobotics Vision 60 Firmware

0.27.2

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the communication protocol of Ghost Robotics Vision 60 robots could allow an unauthorized external party to gain full control of the robot by impersonating a legitimate control station. This is due to the absence of encryption and authentication in the MAVLink-based protocol, making it possible to intercept and replicate commands.

  • Unencrypted robot commands can be hijacked.
  • Gaining unauthorized robot control is possible.
  • Confirm relevance; widespread external exposure is unlikely.

Attack Path

How an attacker could exploit the issue

An attacker could compromise a Ghost Robotics Vision 60 by exploiting its communication protocol, which lacks encryption and authentication. By capturing legitimate traffic, an attacker can impersonate the control station and issue unauthorized commands to the robot. This can be achieved remotely via Wi-Fi or 4G/LTE, with the MAVLink protocol's public documentation increasing the likelihood of attack.

  • Attack requires network access.
  • Attacker sends crafted commands.
  • Complete robot control is possible.

Live Threat

Current exploitation, exposure, and threat context

An attacker could gain unauthorized full control of a robot by impersonating its control station. This is possible because the robot's communication protocol lacks encryption and authentication, allowing an attacker to capture and replay traffic or send arbitrary commands over Wi-Fi or 4G/LTE connections.

  • Robot control and functionality.
  • Unauthenticated command injection.
  • Compromised robot operation.

Operational Fix

Recommended remediation, mitigation, and detection steps

Attackers can exploit a communication protocol vulnerability to gain unauthorized control of Ghost Robotics Vision 60 robots. Real-world ownership likely falls to the teams managing the robot fleet and their associated control systems, such as robotics or operational technology (OT) teams, possibly in coordination with network and security teams. The first practical step is to identify all Vision 60 units, confirm their network exposure and operational criticality, and then engage the accountable owner to plan remediation according to risk.

  • Robotics or OT team should own.
  • Verify network reachability and criticality.
  • Plan remediation based on operational risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Ghost Robotics Vision 60?

The Vision 60 is an advanced quadrupedal robot designed for autonomous navigation and operational tasks in various environments. It relies on specific firmware, version 0.27.2, to manage its movements and functions via a communication interface. These robots are typically managed by robotics or operational technology teams for specialized field deployments, utilizing wireless connectivity like Wi-Fi or 4G/LTE to receive instructions from a dedicated control tablet.

What does CVE-2025-41108 mean for the robot's security?

This CVE highlights a critical weakness categorized as CWE-287, which refers to improper authentication. In plain terms, the robot's communication protocol lacks the security safeguards—specifically encryption and authentication—needed to verify the sender of a command. Because of this, the robot cannot distinguish between its legitimate operator and an unauthorized person, potentially allowing an attacker to seize full control.

How does an attacker trigger this vulnerability?

An attacker triggers this by intercepting the communication link between the robot and its control station. Since the MAVLink-based protocol is unencrypted, an attacker can capture legitimate traffic and replicate it to send their own malicious commands. Note that simply being near the robot is not enough; the attacker must have network access to the Wi-Fi or 4G/LTE path used for remote control to successfully impersonate the control station.

Is my robot at risk from the internet?

According to Halo Surface Signal, public internet exposure for the Vision 60 is unlikely. These robots are usually operated within localized environments or specialized private networks rather than as standard web-facing services. While remote command injection is technically possible via Wi-Fi or 4G/LTE, the device's typical deployment model means it is generally not exposed to the broader public internet.

What should I do if I am running this technology?

Start by identifying all Vision 60 units currently in your environment. Evaluate the network reachability of these devices to determine if they are accessible over broader networks and assess their operational criticality. Once you have a clear picture of your fleet's status, coordinate with your robotics or operational technology teams to discuss appropriate security mitigations based on your specific risk profile.

References