Unitree Go2 firmware versions V1.1.7 through V1.1.9 and V1.1.11 (EDU) do not implement DDS authentication or authorization for the Eclipse CycloneDDS topic rt/api/programming_actuator/request handled by actuator_manager.py. A network-adjacent, unauthenticated attacker can join DDS domain 0 and publish a crafted message (api_id=1002) containing arbitrary Python, which the robot writes to disk under /unitree/etc/programming/ and binds to a physical controller keybinding. When the keybinding is pressed, the code executes as root and the binding persists across reboots.
Security readout for executives and security teams
Plain-English summary
This flaw lets someone on the same local network plant code on a Unitree Go2 robot without logging in. The code runs only after a mapped controller key is pressed, but it then runs as root and can survive reboot. This is high business risk for labs, demonstrations, and production sites using affected robots on shared networks.
Executive priority
Prioritize remediation where Go2 robots share networks with laptops, visitors, lab systems, or public demo infrastructure. The combination of unauthenticated adjacent access, root execution, persistence, and physical robot impact justifies high priority even without confirmed active exploitation.
Technical view
Affected Go2 firmware lacks DDS authentication and authorization on a CycloneDDS actuator programming topic. An adjacent unauthenticated participant can publish a crafted programming request that stores Python under /unitree/etc/programming/ and binds it to a controller action. Execution requires the bound keypress, then runs with root privileges and persists.
Likely exposure
Exposure is mainly robots running Unitree Go2 firmware V1.1.7 through V1.1.9 or V1.1.11 EDU on networks where untrusted adjacent systems can reach DDS domain 0. Internet exposure is not indicated by the sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed in-the-wild exploitation. Public technical details and an exploit-tagged reference exist, so defenders should assume capable researchers can reproduce the issue on reachable affected robots.
Researcher notes
The key constraints are adjacent network access and user interaction via controller keypress. The affected behavior is tied to CycloneDDS topic rt/api/programming_actuator/request and actuator_manager.py handling. Sources do not name a vendor patch, broader model impact, or confirmed exploitation.
Mitigation direction
Check Unitree guidance for fixed firmware or official mitigation.
Keep affected robots off shared, guest, or untrusted Wi-Fi networks.
Restrict DDS traffic to trusted robot-control hosts only.
Review and remove unauthorized programming files or keybindings.
Treat affected robots as safety-relevant assets during demonstrations and operations.
Validation and detection
Inventory Unitree Go2 firmware versions in use.
Identify any V1.1.7 through V1.1.9 or V1.1.11 EDU devices.
Confirm DDS domain 0 is not reachable from untrusted adjacent hosts.
Inspect /unitree/etc/programming/ for unexpected files.
Review controller bindings for unknown programmed actions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.