Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 070
No. 070 Critical Brief · Agent Authority Proof

Unitree: Researchers showed its humanoid and quadruped robots could be taken over with root access via Bluetooth setup (researchers, NVD)

1key
One encryption key shared by every unit. Extracted from one robot, it worked on the others (NVD, researchers)
4models
Affected models: the G1 and H1 humanoids and the Go2 and B2 quadrupeds (NVD)
2025-05→09-20
From the researchers contacting Unitree to public disclosure. The researchers say Unitree stopped replying in July (IEEE Spectrum)
CountryGlobal
Incident date2025-09-20
Published2026-06-19
Revised v2.1 · 2026-11-02
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

The researchers showed that every unit used the same encryption key, and that a handshake containing the string “unitree” was enough to pass authentication. The reports we consulted describe no real-world exploitation. Unitree said it had completed most fixes, but until updates arrive, the same key still opens the entry point. If every unit holds the same key, a key taken from one unit opens the entry point of all the others.

Exhibit 1Detection vs pre-execution check

A pre-execution check means checking the connecting party against a per-unit key before accepting the connection. Detection means noticing a takeover or outbound data afterwards. The dates below are when the researchers, NVD and Unitree published each point, not when a takeover became possible.

Pre-execution check · not known from the disclosuresCheck the party against a per-unit key before accepting the connection
What was confirmedWith the shared key, taken over as root
from the setup entry point (researchers' demonstration)
Detection · partialResearchers found it; fixes in progress
2025-05
Researchers contact Unitree
09-17
Paper posted to arXiv
09-20
UniPwn disclosed
09-29
Unitree says most fixes are done

What got through

What got through
A connection to the Bluetooth setup entry point, and strings sent there as a Wi-Fi network name or password. A handshake made with the shared key passed authentication, and commands slipped into those strings were executed as root (the top-level privilege) when the Wi-Fi settings were applied (CVE-2025-60250, 60251, 35027, 60017).
What reached the receiving side
In general, at an entry point with no per-unit key, a connection with a matching handshake arrives as the same “correct connection” whoever it comes from. An attacker using an extracted key cannot be told apart from the genuine setup app at the entry point.
Spread to other units
The researchers say a compromised robot could look for other Unitree robots within Bluetooth range and take them over automatically.
Not disclosed
Real-world exploitation (the reports we consulted describe none), and whether the fix updates had shipped (not confirmed as of IEEE Spectrum’s article, updated 2025-11).

Pre-execution check

Whatever the route, the condition for telling them apart is that whoever accepts connections at an entry point such as setup checks the connecting party, before accepting it, against a key or certificate unique to that unit.

The core of this case
If every unit holds the same key, a key taken from one unit opens the entry point of all the others.
Who approves
The device vendor. It issues a unique key or certificate for each unit, and never builds the same secret into every unit. The connecting party answers with the key that matches that unit.
Where it is checked
The part of the unit that accepts connections at setup and similar entry points. A connection whose key does not match is not accepted. Input that is accepted is still validated before use, and strings received as a Wi-Fi name or password are not passed straight into execution.
What is recorded
Which party connected to which unit with which key. What the device sends to outside servers is also made visible to the deploying organization.

Researchers found and reported it, and Unitree worked on fixes, but fixes come after discovery. A similar case, where outside commands were run through an entry point, is Universal Robots PolyScope (outside commands could be run through an industrial robot’s control screen).

What Lemma does

Lemma builds the pre-execution check into the side that accepts connections at setup and similar entry points. It does not look for intrusions; it checks, before the connection is accepted, that the connecting party holds the key unique to that unit.

Industries and operations to watch

IndustryManufacturing & core infrastructure
Organizations that build robots or connected devices, and those that deploy them in factories and facilities.
IndustryGovernment & public sector
Organizations trialing robots for security or inspection (IEEE Spectrum noted UK police testing a Go2).

Current controls vs Lemma

The route in this case is column 1 (a connection to the setup entry point) and column 2 (running a string that arrives through that entry point). Column 3 is units that have not yet received the fix; shipped updates had not been confirmed as of the 2025-11 report.

Control Connection to the setup entry point Running a string from the entry point Units without the update
Encrypting communications Not effective Not relevant Not relevant
Handshake authentication Not effective Not relevant Not relevant
Network segmentation Partial Not relevant Not relevant
Firmware updates Not relevant Not relevant Partial
Lemma (pre-execution check) Effective Partial Not effective

Encrypting communications did not help because the key was the same on every unit. Handshake authentication passed anything containing “unitree”. Network segmentation can restrict Wi-Fi traffic, but anyone nearby can reach the Bluetooth entry point. Firmware updates: Unitree said most fixes were done, but no shipped update had been confirmed. Lemma checks the party against a per-unit key before accepting the connection.

Note: Lemma’s check works only on units that carry a unique key or certificate and have the check built into the part that accepts connections. Units that do not get the update keep the same key scheme, so the check does not apply to them. It passes if a unit’s own key has been extracted, or if the genuine setup app has been taken over. Validation that keeps input strings out of execution is something the device maker adds separately. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three things to confirm for organizations that build or deploy robots and connected devices

  • Have you confirmed with the vendor that strings arriving through device setup are never executed as-is?
  • Do you know what your deployed devices send to outside servers?
  • Do you have a procedure for receiving and installing firmware updates from the vendor?

Facts and timeline

Researchers
Andreas Makris and Kevin Finisterre found and disclosed the flaws. With Víctor Mayoral-Vilches of Alias Robotics, they posted a paper on the G1’s security to arXiv (2025-09).
Affected models
The G1, H1, Go2 and B2, which share common firmware (NVD).
Entry point
The Bluetooth setup used to connect the robot to Wi-Fi.
Why authentication passed
The same encryption key and initialization vector (IV) were built into every unit (CVE-2025-60250), and any handshake containing the substring “unitree” was accepted (CVE-2025-60251).
Root execution
Commands slipped into strings sent as the Wi-Fi network name or password were executed as root when the Wi-Fi settings were applied (CVE-2025-35027, CVE-2025-60017).
Spread to other units
The researchers say a compromised robot could look for other Unitree robots within Bluetooth range and take them over automatically.
Weak configuration encryption
The paper says the encryption protecting settings also relied on a fixed scheme and predictable values.
Outbound data
The paper says the robot sent sensor and status data to two outside servers every 300 seconds without telling the operator.

Glossary
Bluetooth setup — The entry point used to connect a robot to Wi-Fi, by sending settings over Bluetooth from a nearby phone.
Root (root access) — The administrator level that can do anything on a device. Whoever holds it can control the device at will.
Firmware — The software that runs inside a device. Updates come from the vendor.

Timeline

  • The researchers contact Unitree.
  • Makris publishes the keys on X. The researchers say Unitree stopped replying from this month (IEEE Spectrum).
  • The paper is posted to arXiv.
  • The researchers disclose UniPwn.
  • The CVEs are published in the NVD.
  • Unitree says on LinkedIn that most fixes are done.

The facts rely on the researchers’ paper (primary), the NVD CVE records and IEEE Spectrum’s reporting. This is a research demonstration, and the reports we consulted describe no real-world exploitation. This Brief does not assign blame to the manufacturer; its subject is the shared key and the missing input validation. What has not been disclosed does not mean there were no controls. This attack requires being within Bluetooth range. We will revise this Brief if Unitree announces that updates have shipped.

After disclosure

  • Unitree: On 29 September it said on LinkedIn that it had begun addressing the concerns immediately, had completed most fixes, and would roll out updates soon (IEEE Spectrum). Whether updates had shipped was not confirmed as of IEEE Spectrum’s article (updated 2025-11).
  • Researchers: Argued in the paper that defenses are needed as humanoid robots move into critical infrastructure.

Sources

  1. Research, primaryarXiv Mayoral-Vilches, Makris, Finisterre, “Cybersecurity AI: Humanoid Robots as Attack Vectors”2025-09-17 · arxiv.org/abs/2509.14139
  2. Primary, CVENVD “CVE-2025-35027” (2025-09-26) — related: CVE-2025-60250, CVE-2025-60251, CVE-2025-60017nvd.nist.gov/vuln/detail/CVE-2025-35027
3 more (reporting, analysis)
  1. PressIEEE Spectrum “Exploit Allows for Takeover of Fleets of Unitree Robots”2025-09-25 · spectrum.ieee.org/unitree-robot-exploit
  2. PressHelp Net Security “Humanoid robot found vulnerable to Bluetooth hack, data leaks to China”2025-10-16 · helpnetsecurity.com/2025/…
  3. PressHackaday “Unitree Humanoid Robot Exploit Looks Like A Bad One”2025-09-30 · hackaday.com/2025/…

References: “The last layer left in AI-era cyber defense”

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"Unitree: Researchers showed its humanoid and quadruped robots could be taken over with root access via Bluetooth setup (researchers, NVD)".
Lemma Critical Brief No.070. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/070-unitree-shared-key-robot-identity/
Read nextNext
All Briefs →
Revision History

Current version: 2.1

Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.