Unitree Go2 vulnerability alert graphic urging a firmware update to 1.1.11.5

Unitree Go2 Vulnerability: Update Your Robot Dog to Firmware 1.1.11.5 Now

The Unitree Go2 vulnerability tracked as CVE-2026-115995 is a critical bug in the robot dog’s AI chat feature, and the fix is firmware 1.1.11.5. If your Go2 runs 1.1.11.4 or older, update it now.

The flaw was disclosed on October 24, 2026, and scores 9.6 out of 10. A second, milder bug was published the same day.

  • Affected: Unitree Go2 firmware up to 1.1.11.4
  • Fixed in: firmware 1.1.11.5 (Edu, Max, Pro and X packages)
  • Severity: 9.6 CVSS, remote attack, needs some user interaction
  • Public exploit: none reported so far
  • Disclosed: October 24, 2026

Those five lines are the whole story for most owners. The rest explains what the bug does, how serious it is, and what to do about it.

What the Unitree Go2 vulnerability actually does

The bug sits in the robot’s chat AI component, in a function called set_volume. It doesn’t clean up the value it receives, so an attacker can sneak operating-system commands into it.

According to The Hacker Wire, the attack can be launched over the network with no login. The CVSS vector says a user has to do something first, like open a link or connect to a bad source.

In plain terms, a successful attack could let someone run commands on the robot. That matters because the Go2 has a camera, microphones and moving legs.

Why robot dog security is a bigger deal than it sounds

A bug in a phone app usually risks your data. A bug in a robot can touch the physical world too, since the Go2 walks around your home or workplace with a camera on board.

Robots like this also ship with AI chat and voice features that talk to cloud services. Every connection like that is another door that has to be built carefully.

This is why a “set the volume” function turning into a command-injection hole feels so avoidable. Input checking is basic security hygiene, and it’s the kind of mistake that tends to show up when AI features are added fast to hardware that wasn’t designed around them.

It also means the Go2 firmware update isn’t optional housekeeping. Treat it like a phone security patch, not a feature release you can skip.

Is anyone attacking Go2 robots yet?

Not that anyone has reported. VulDB says no public exploit is available, though the technical details are known.

The Hacker Wire lists a 1.38% chance of exploitation in the next 30 days and no entry in the CISA known-exploited list. That’s low, but those numbers can change fast once a bug gets attention.

Unitree confirmed the report, which VulDB says matches its internal ticket #474. A confirmed bug with public details is exactly when you should patch, not wait.

Two bugs, two very different risk levels

A second flaw, CVE-2026-115996, landed the same day in the same chat component. It’s far less dangerous, but the two are easy to mix up.

Item CVE-2026-115995 CVE-2026-115996
Flaw type OS command injection Improper TLS certificate validation
Severity 9.6, critical 3.7, medium
Where set_volume in the chat AI module WebSocket client in the same module
Affected firmware 1.1.11.4 and earlier Up to 1.1.13 (listing also names 1.1.14.1 and 1.1.15.1)
Fix Firmware 1.1.11.5 No official patch listed yet

Per OffSeq, the second bug means the robot’s secure connection doesn’t properly check the server’s certificate. That could let someone on your network tamper with traffic. No official patch is listed for it yet.

The version ranges don’t line up neatly between the two, and the listings themselves disagree in places. Check Unitree’s own security page for the final word.

How to update your Go2 firmware and lower the risk

Start by checking which firmware you run. Then install 1.1.11.5 or newer from Unitree’s official package for your model.

If you can’t tell which version you have, open the robot’s companion app and look at the device or firmware screen. Write the number down before you update so you can confirm the change afterward. If you manage several robots at a school or lab, check each one, because they often sit on different versions.

While you wait for fixes to the second bug, a few habits help:

  • Keep the robot off public Wi-Fi and shared networks.
  • Skip unknown links or pairing requests that involve the robot or its app.
  • Turn off the AI chat feature if you don’t use it.

These steps cut the odds, but they don’t replace the patch. Security teams treat command-injection bugs the same way everywhere. We saw the same pattern in our guides on the GitLab CVE-2026-97229 patch and the Node2Shell Node.js fix.

Frequently Asked Questions

Which Unitree Go2 firmware is affected by CVE-2026-115995?

Versions up to and including 1.1.11.4 are affected. Firmware 1.1.11.5 fixes it.

Can someone take over my robot dog remotely?

The flaw is rated remote, but it needs some user interaction and no working exploit has been made public. Patching removes the risk.

Where do I get the Go2 update?

Use Unitree’s official firmware package for your Go2 model (Edu, Max, Pro or X). Avoid third-party downloads.

Is the second Go2 bug fixed?

Not yet, as far as public listings show. It’s rated medium at 3.7, so it’s less urgent than the command-injection bug.

Our take: patch first, then rethink AI features on gadgets

Update to 1.1.11.5 today, it takes a few minutes and closes the serious hole. The bigger lesson is that a chatty AI feature adds attack surface to any device with sensors and motors, so switch off what you don’t use.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *