"Two independent root remote code execution chains" — those are the words researcher Olivier Laflamme used on August 27, 2026, to describe two separate exploits that reach root on the Unitree G1 EDU's Locomotion PC, tracked as CVE-2026-76639 and CVE-2026-76640.
CVE-2026-76639: chat_go path-traversal to bashrunner yields root on the Locomotion PC
Laflamme's disclosure describes CVE-2026-76639 as a network-adjacent chain that begins with a path-traversal condition in the chat_go component and reaches bashrunner. Successful execution through bashrunner results in root code execution on the robot's Locomotion PC. Laflamme characterized this as an independent remote code execution (RCE) primitive, and he reused it as a component in demonstrating the separate Bluetooth chain.
CVE-2026-76640: BLE bootstrap plus cloud key-recovery leads to a Wi‑Fi provisioning buffer overflow
The second chain, CVE-2026-76640, begins from Bluetooth Low Energy (BLE) proximity. Laflamme reported that an initial BLE write path accepts a bootstrap interaction without the device having performed Bluetooth pairing; however, the bootstrap material itself remains protected and later Wi‑Fi provisioning operations require the application's authenticated BLE state.
During testing, Unitree's cloud service accepted a valid Unitree account for a key-recovery request without verifying that the account actually owned the supplied robot. That authorization gap allowed the account to recover key material associated with another G1 EDU. The recovered key could then be used to establish the authenticated BLE state required by the Wi‑Fi provisioning operations. From that state, Laflamme documented a buffer overflow in the Wi‑Fi provisioning code that produced root execution on the Locomotion PC.
Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleUnitree's immediate remediation and firmware status
Laflamme said Unitree patched the cloud account-to-robot ownership check in July 2026. As of his August 27 disclosure, the cloud-assisted route now requires an account bound to the target G1 or the relevant key material already in hand. An exact fixed firmware release for either vulnerability has not been verified in any accessible Unitree guidance, leaving G1 EDU owners without a confirmed firmware release target for remediation.
In his technical disclosure Laflamme also noted that he upgraded his test robot to V1.5.2 during research; that sequence does not by itself establish V1.5.1.1 as affected.
Testing details and the published proof-of-concept
Laflamme limited his propagation test to two G1 robots in one room. He described the two issues as separate root-RCE paths and reused CVE-2026-76639 as one disclosure primitive while demonstrating the BLE chain tracked as CVE-2026-76640. He reported that Unitree's cloud authorization fix breaks that exact proof-of-concept flow.
What this means for technologists, procurement leaders, and G1 EDU owners
- Technologists and security teams: The two chains demonstrate distinct technical trust boundaries — a network-adjacent path through chat_go to bashrunner, and a BLE-to-cloud-to-Wi‑Fi-provisioning path that culminates in a buffer overflow. Teams responsible for G1 EDU deployments will need to validate that the cloud account-to-robot ownership check is enforced and to track any firmware advisories that explicitly list mitigations for CVE-2026-76639 and CVE-2026-76640.
- Procurement and program managers: Unitree's official product page distinguishes the G1 and G1 EDU as separate models, and the broader applicability of these two vulnerabilities to other Unitree robots remains unconfirmed. Procurement decisions should therefore await clear vendor guidance about which models and firmware versions are affected and which firmware releases contain fixes.
- G1 EDU owners and operators: At the time of the disclosure, an exact fixed firmware release had not been verified in Unitree guidance. The July 2026 cloud-side patch addressed the account-to-robot authorization gap that enabled one proof-of-concept flow, but owners do not have a confirmed firmware version to target for a full remediation.
Olivier Laflamme published the technical research on August 27, 2026. The Hacker News has reached out to Unitree to confirm the fixed firmware versions, the affected product scope, and the current remediation status, and will update the story with any response.
The record Laflamme provided is specific: two distinct RCE chains, both culminating in root on the Locomotion PC, one reachable via a network-adjacent path and the other by chaining BLE bootstrap behavior with a cloud key-recovery gap and a Wi‑Fi provisioning overflow. The immediate operational fact is that Unitree patched the cloud ownership check in July 2026; the remaining, concrete gap is a verified firmware release that explicitly documents fixes for CVE-2026-76639 and CVE-2026-76640.
