Unitree Go2/G1 up to 1.1.7 BLE Module wpa_supplicant_restart.sh os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Unitree Go2 and G1 up to 1.1.7. Affected by this vulnerability is an unknown functionality of the file wpa_supplicant_restart.sh of the component BLE Module. This manipulation causes os command injection. This vulnerability appears as CVE-2025-35027. The attacker needs to be present on the local network. There is no available exploit.
Details
A vulnerability classified as critical was found in Unitree Go2 and G1 up to 1.1.7. Affected by this vulnerability is an unknown functionality of the file wpa_supplicant_restart.sh of the component BLE Module. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Multiple robotic products by Unitree sharing a common firmware, including the Go2, G1, H1, and B2 devices, contain a command injection vulnerability. By setting a malicious string when configuring the on-board WiFi via a BLE module of an affected robot, then triggering a restart of the WiFi service, an attacker can ultimately trigger commands to be run as root via the wpa_supplicant_restart.sh shell script. All Unitree models use firmware derived from the same codebase (MIT Cheetah), and the two major forks are the G1 (humanoid) and Go2 (quadruped) branches.
The weakness was presented by Andreas Makris, Kevin Finisterre and Konstantin Severov. It is possible to read the advisory at takeonme.org. This vulnerability is known as CVE-2025-35027 since 04/15/2025. The exploitation appears to be easy. The attack can only be done within the local network. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/12/2026). The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-31217). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.0
VulDB Temp Score: 8.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.3
CNA Vector (AHA): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/15/2025 CVE reserved09/26/2025 Advisory disclosed
09/26/2025 VulDB entry created
01/12/2026 VulDB entry last update
Sources
Advisory: takeonme.orgResearcher: Andreas Makris, Kevin Finisterre, Konstantin Severov
Status: Not defined
CVE: CVE-2025-35027 (🔒)
GCVE (CVE): GCVE-0-2025-35027
GCVE (VulDB): GCVE-100-325963
EUVD: 🔒
Entry
Created: 09/26/2025 09:09Updated: 01/12/2026 18:17
Changes: 09/26/2025 09:09 (64), 09/28/2025 22:51 (1), 01/12/2026 18:17 (1)
Complete: 🔍
Cache ID: 216:B23:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.