The Robot Has Root. I Am Not Surprised. I Am Tired.

I have been warning anyone who would listen, since approximately 1994, that putting a computer inside a walking metal skeleton and connecting it to anything was a catastrophic idea. Nobody listened. They never do. Now we have humanoid robots with root-level remote code execution vulnerabilities, and one of them starts over Bluetooth. Bluetooth. The protocol I have distrusted since it was invented by people who clearly had never read a threat model in their lives.

Researcher Olivier Laflamme, who deserves a commendation and probably a stiff drink, has disclosed two independent root RCE chains in the Unitree G1 EDU robot. These are tracked as CVE-2026-76639 and CVE-2026-76640. The first chain runs through something called chat_go and bashrunner, which are, I can only assume, named by someone who thought security was someone else's department.

The second chain. Over Bluetooth Low Energy. To the robot's Locomotion PC. Granting root.

A Wolf does not even need to be on your network. He just needs to be nearby, perhaps standing in the parking lot with a laptop and a grievance. This is not a hole in the fence. This is the fence having never been built in the first place.

In the old days, our dangerous machines were connected to nothing. A CNC lathe on a factory floor did not have a Bluetooth radio. It did not have an IP address. It had a power cable and a healthy sense of its own limitations. The Flock was safer for it.

The Shepherds, naturally, looked at a bipedal robot with full root access to its own locomotion systems and thought: yes, let us also give it wireless connectivity. Marvelous. I am sure the liability paperwork will sort itself out.

The Sky Pasture crowd will tell you this is an edge case. It is not an edge case. It is a preview.

Remediation

These are my instructions. Follow them without complaint.

• Disable Bluetooth immediately. It was a mistake to enable it. Correct the mistake.
• Apply the manufacturer's patches when available. I know. I know. Shearing the robot feels undignified. Do it anyway.
• Network-segment these devices. They should not be talking to anything they do not absolutely need to talk to. Treat them like a new lamb: quarantine first, trust never.
• Audit bashrunner. Any service with that name in a production environment is a cry for help.
• Do not put humanoid robots on your operational network. Write that down. Frame it.

If your security strategy for a walking robot depends on hoping nobody nearby owns a Bluetooth adapter, you have already lost.

Stay paranoid, the machines certainly aren't.

Original Report: https://thehackernews.com/2026/08/two-unitree-g1-edu-humanoid-robot-flaws.html