Adjacent control bypass via hard-coded BLE cryptography
Published Sep 26, 2025 · Updated Sep 26, 2025
Hard-coded cryptography in Unitree Go2, G1, H1, and B2 devices through 2025-09-20 allows adjacent attackers to forge BLE commands. The BLE receive manager decrypts every packet with one device-independent AES-CFB key and IV, so published protocol details provide the material needed to create accepted ciphertext. Attackers must be within BLE range; the exposed key defeats packet authentication and permits accepted control messages without prior credentials.
Summary
What happened
Hard-coded cryptography in Unitree Go2, G1, H1, and B2 devices through 2025-09-20 allows adjacent attackers to forge BLE commands. The BLE receive manager decrypts every packet with one device-independent AES-CFB key and IV, so published protocol details provide the material needed to create accepted ciphertext. Attackers must be within BLE range; the exposed key defeats packet authentication and permits accepted control messages without prior credentials.
The record
- CVE
- CVE-2025-60250
- Published
- Sep 26, 2025
- Updated
- Sep 26, 2025
- Vendor
- Unitree Robotics
- Product
- Unitree Go2
- Classifications
- CWE-321, T1552
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2025CVE publishedPublication date reported by the CVE source.
- Sep 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2025-09-20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- UniPwnfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo