CVE-2026-12991: Ghost Robotics Vision 60 Auth Bypass Flaw

CVE-2026-12991 Overview

CVE-2026-12991 affects the Ghost Robotics Vision 60 quadruped robot running APK v5.5.0. The device lacks cryptographic mechanisms to guarantee the integrity and authenticity of communications between the operator and the robot. An attacker on the same local network can perform Address Resolution Protocol (ARP) spoofing and selectively block traffic to intercept and manipulate control packets. This allows the adversary to disconnect the legitimate operator, take over the session, and prevent the operator from regaining control. The weakness is classified under CWE-300 (Channel Accessible by Non-Endpoint).

Critical Impact
An adjacent-network attacker can hijack control of a Vision 60 robot, compromising the confidentiality, integrity, and availability of field operations.

Affected Products

Ghost Robotics Vision 60 quadruped robot
Vision 60 controller APK version 5.5.0
Operator-to-robot communication channel

Discovery Timeline

2026-07-27 - CVE-2026-12991 published to the National Vulnerability Database (NVD)
2026-07-27 - Last updated in NVD database

Technical Details for CVE-2026-12991

Vulnerability Analysis

The Vision 60 robot communicates with its operator application over the local network without cryptographic integrity or authenticity protections. Packets exchanged between the controller and the robot are neither signed nor authenticated at the message level. This design gap makes it possible for a network-adjacent attacker to insert themselves into the communication path and act as a trusted party. The lack of mutual authentication means the robot cannot distinguish between the legitimate operator and an attacker-controlled endpoint. Because the channel also fails to bind session identity to a verified cryptographic key, session takeover requires no credential compromise.

Root Cause

The root cause is the absence of message authentication and integrity controls in the Vision 60 control protocol. There is no verified handshake, no per-message signature, and no channel binding tying operator sessions to a trusted key. This aligns with CWE-300, where a third party can position itself on the communication path and act as a non-endpoint intermediary.

Attack Vector

The attacker must reside on the same local or adjacent network segment as the robot and the operator. The typical sequence is:

The attacker performs ARP spoofing to poison the ARP caches of the operator device and the robot, redirecting traffic through the attacker's host.
The attacker selectively blocks or forwards packets to disrupt the legitimate operator's control session.
Once the operator's session is severed, the attacker issues crafted control packets to the robot from their own endpoint.
The attacker continues to filter traffic so that the original operator cannot re-establish a working session.

Because no cryptographic verification is performed, the robot accepts commands from the attacker as if they originated from the authorized controller. Refer to the INCIBE Security Notice for coordinated advisory details.

Detection Methods for CVE-2026-12991

Indicators of Compromise

Sudden ARP table changes on the operator workstation or the robot's network interface, especially duplicate MAC-to-IP mappings.
Unexplained session drops on the operator console followed by continued robot activity.
Unexpected control traffic sourced from a host that is not the registered operator device.
Bursts of gratuitous ARP replies on the operational network segment.

Detection Strategies

Deploy ARP inspection or Dynamic ARP Inspection (DAI) on managed switches serving the robot's operational network.
Monitor for repeated ARP announcements binding the robot's IP to different MAC addresses within short intervals.
Baseline the operator-to-robot traffic pattern and alert on new source endpoints issuing control packets.
Capture and analyze wireless or wired traffic during missions to identify duplicated or reordered control frames.

Monitoring Recommendations

Log all ARP activity and Layer 2 anomalies from switches supporting the robot deployment environment.
Track operator authentication events and correlate them with unexpected disconnect or reconnect patterns.
Alert on any device joining the operational VLAN that is not on an approved allowlist.

How to Mitigate CVE-2026-12991

Immediate Actions Required

Isolate the Vision 60 robot and its controller on a dedicated, tightly access-controlled network segment or VLAN.
Restrict wireless access to the operational network using WPA3-Enterprise with certificate-based client authentication.
Enforce Dynamic ARP Inspection and DHCP snooping on switches serving the robot network.
Contact Ghost Robotics for firmware and APK updates addressing missing communication integrity controls.

Patch Information

No vendor patch is referenced in the NVD entry for CVE-2026-12991 at the time of publication. Operators should consult the INCIBE Security Notice and coordinate directly with Ghost Robotics for remediation timelines and firmware updates for APK v5.5.0 and later.

Workarounds

Operate the robot only on physically isolated networks with no untrusted clients present.
Terminate operator-to-robot traffic inside an authenticated VPN tunnel that provides message integrity and endpoint authentication.
Disable any unused wireless interfaces on the operator workstation to reduce the ARP spoofing attack surface.
Continuously monitor the operational segment with a passive network sensor during active missions.

bash

# Example: enable Dynamic ARP Inspection on a Cisco switch VLAN hosting the robot
configure terminal
ip arp inspection vlan 20
interface GigabitEthernet0/1
  ip arp inspection trust
exit
ip dhcp snooping
ip dhcp snooping vlan 20
end