Public disclosure
Reported by Víctor Mayoral-Vilches; Andreas Makris; Kevin Finisterre (authors of the cited papers).
Security advisory
Unitree G1 telemetry privacy findings disputed by the manufacturer
The researchers report G1 telemetry transmissions of sensor and service-state data without explicit operator notice or consent. Unitree states that internet access requires user configuration and authorization, and that connected robots may send serial-number and health-state data. Unitree denies collecting private or sensitive data without authorization.
Records last verified Oct 13, 2026 · Send a correction
- CVE IDs
- No CVE recorded
- Class
- Privacy
- CVSS / assessor
- No published CVSS
- Vendor response
- Disputed
Other disclosure identifiers: arXiv:2509.14096, arXiv:2509.14139
Affected models, versions and components
- Unitree G1
Affected versions not stated
Component: Telemetry and remote health monitoring
Disclosure and response timeline
The record has one response or remediation date. It does not supply separate dates for every vendor communication and fix.
Vendor response / remediation update (as recorded)
Disputed. Unitree disputes unauthorized private or sensitive data collection. No fixed release is identified.
Fix
Separate fix date not recorded
No fixed version identified in the recorded sources.
What owners should do
Review internet-connectivity authorization as described in Unitree's statement.
Fixed version (as stated): No fixed version identified.
Unitree disputes unauthorized private or sensitive data collection. No fixed release is identified.
How to read this ledger
We include official CVE records, vendor advisories, CERT/CISA notices and researchers’ own disclosures. CVSS is attributed to its published assessor, including the named CVE Numbering Authority (CNA), with the version from the recorded vector. A CNA score is not an NVD assessment. An unpublished score stays unknown.
Affected versions, variants, component scope and fix qualifications retain the disclosure’s wording. A reported patch is not an independent retest. Disputed findings show the researcher and vendor positions together. We publish no exploit instructions or payloads.
Counts describe curated advisory records; several records may come from one disclosure. Coverage is incomplete and is not a security ranking. An absent record does not establish that a robot has no vulnerabilities.
Evidence
Sources
- [s1] The Cybersecurity of a Humanoid Robot ↗
Víctor Mayoral-Vilches / arXiv · paper · published Sep 17, 2025 · accessed Oct 13, 2026
- [s2] Cybersecurity AI: Humanoid Robots as Attack Vectors ↗
Víctor Mayoral-Vilches, Andreas Makris, and Kevin Finisterre / arXiv · paper · published Sep 23, 2025 · accessed Oct 13, 2026
- [s3] Statement to our respected Unitree users ↗
Unitree Robotics · official · published Sep 29, 2025 · accessed Oct 13, 2026
Other advisory records
- Unitree G1 EDU BLE provisioning and buffer handling allow root code execution →
- Unitree G1 EDU remote code execution through DDS bridge and file upload →
- Unitree UPK firmware-update format uses hardcoded cryptographic keys →
- Unitree G1 and H1 access-point configuration command injection →
- Unitree G1 and H1 BLE provisioning handshake authentication bypass →
- Unitree G1 and H1 BLE provisioning uses shared cryptographic secrets →
- Unitree G1 and H1 Wi-Fi configuration command injection →
Trackers
Task evidence →
Source statements, stated autonomy and demonstration conditions.
Deployments →
Customers, tasks, contracts and evidence grades.
Timelines →
Dated maker claims, targets and sourced outcomes.
Policy →
Market access, legislation and standards in context.
How many robots →
Estimates, definitions, capacity and forecasts.