Vision 60
Monthly
Man-in-the-middle attack against Ghost Robotics Vision 60 robot firmware v5.5.0 allows local network attackers to intercept and manipulate communications, disconnect legitimate operators, and take unauthorized control of the quadruped robot, completely compromising confidentiality, integrity, and availability of operations. No active exploitation has been reported in CISA KEV, and no public exploit code was identified at time of analysis.
Ghost Robotics Vision 60 mobile app (APK v5.5.0) fails to enforce single-client sessions, allowing an unauthenticated attacker with a modified app on the adjacent network to connect to the robot while a legitimate operator is active. The attacker can intercept real-time video and send commands without alerting the legitimate user, compromising confidentiality and operational control. No active exploitation or public exploit code has been identified; a vendor patch is available.
We need to produce a JSON output for CVE-2026-12989 based on provided data. Multi-source synthesis. We'll go through each field. First, product_name: "1-3 words ONLY. The specific product or service name affected. Examples: 'Apache Tomcat', 'WordPress', 'Linux Kernel', 'nginx-ui', 'GoAnywhere MFT'. NOT the vulnerability type, NOT the vendor alone, NOT a description. If multiple products, pick the primary one." The only product is Vision 60 robot from Ghost Robotics. So "Ghost Robotics Vision 60" or just "Vision 60". But the instruction says 1-3 words. "Vision 60" is two words, or "Ghost Robotics Vision 60" is three. I'd go with "Vision 60" as the product name. But we might need to include vendor? The example "Apache Tomcat" includes project. "Ghost Robotics Vision 60" is three words. However, product_name might be just "Vision 60". I'll check: the CPE is cpe:2.3:a:ghost_robotics:vision_60. So product is vision_60. So I'll output "Vision 60". To be safe, "Ghost Robotics Vision 60" may be too long, but it's three words. I'll use "Vision 60" as the core product. The examples like "Cortex XDR agent" — it's three words. So "Vision 60" is fine. Actually "Vision 60 robot" is 3. I'll use "Vision 60". summary: "2-3 sentence plain-language summary for security professionals. CRITICAL: Do NOT copy or paraphrase the Description — write an original synthesis using all available data. Do NOT start with 'A vulnerability', 'A problem', 'A flaw', or 'An issue'. Start with the specific impact verb and product, e.g. 'Remote code execution in Apache Tomcat 9.x allows...' or 'Cortex XDR agent on macOS can be disabled by local admins via...'" So start with "Unauthenticated access to the web administration interface and HTTP API of Ghost Robotics Vision 60 robot (APK v5.5.0) allows...". Actually description: "A lack of authentication in the mobile app (APK v5.5.0) for Ghost Robotics' Vision 60 robot allows an unauthenticated attacker connected to the device's internal Wi-Fi network to g
Man-in-the-middle attack against Ghost Robotics Vision 60 robot firmware v5.5.0 allows local network attackers to intercept and manipulate communications, disconnect legitimate operators, and take unauthorized control of the quadruped robot, completely compromising confidentiality, integrity, and availability of operations. No active exploitation has been reported in CISA KEV, and no public exploit code was identified at time of analysis.
Ghost Robotics Vision 60 mobile app (APK v5.5.0) fails to enforce single-client sessions, allowing an unauthenticated attacker with a modified app on the adjacent network to connect to the robot while a legitimate operator is active. The attacker can intercept real-time video and send commands without alerting the legitimate user, compromising confidentiality and operational control. No active exploitation or public exploit code has been identified; a vendor patch is available.
We need to produce a JSON output for CVE-2026-12989 based on provided data. Multi-source synthesis. We'll go through each field. First, product_name: "1-3 words ONLY. The specific product or service name affected. Examples: 'Apache Tomcat', 'WordPress', 'Linux Kernel', 'nginx-ui', 'GoAnywhere MFT'. NOT the vulnerability type, NOT the vendor alone, NOT a description. If multiple products, pick the primary one." The only product is Vision 60 robot from Ghost Robotics. So "Ghost Robotics Vision 60" or just "Vision 60". But the instruction says 1-3 words. "Vision 60" is two words, or "Ghost Robotics Vision 60" is three. I'd go with "Vision 60" as the product name. But we might need to include vendor? The example "Apache Tomcat" includes project. "Ghost Robotics Vision 60" is three words. However, product_name might be just "Vision 60". I'll check: the CPE is cpe:2.3:a:ghost_robotics:vision_60. So product is vision_60. So I'll output "Vision 60". To be safe, "Ghost Robotics Vision 60" may be too long, but it's three words. I'll use "Vision 60" as the core product. The examples like "Cortex XDR agent" — it's three words. So "Vision 60" is fine. Actually "Vision 60 robot" is 3. I'll use "Vision 60". summary: "2-3 sentence plain-language summary for security professionals. CRITICAL: Do NOT copy or paraphrase the Description — write an original synthesis using all available data. Do NOT start with 'A vulnerability', 'A problem', 'A flaw', or 'An issue'. Start with the specific impact verb and product, e.g. 'Remote code execution in Apache Tomcat 9.x allows...' or 'Cortex XDR agent on macOS can be disabled by local admins via...'" So start with "Unauthenticated access to the web administration interface and HTTP API of Ghost Robotics Vision 60 robot (APK v5.5.0) allows...". Actually description: "A lack of authentication in the mobile app (APK v5.5.0) for Ghost Robotics' Vision 60 robot allows an unauthenticated attacker connected to the device's internal Wi-Fi network to g