Case · DiggingBeagle record

Unitree Go2 chat volume parameter could cross into shell execution

CVE-2026-115995 describes shell-command injection through a Go2 chat_go set_volume value; the advisory lists firmware fix 1.1.11.5. A deployed robot takeover or motion-control exploit has not been independently documented.

Scope

The listing is an advisory rather than an independently observed intrusion; callers, firmware variation, process identity, and any ability to affect locomotion are not fully established.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
not established
Evidence
Grade B
Remediation
patch available
AI role
AGAINST AI
Basis and provenance

Enrich update: CLM-ENRICH-20261027-37 cites SRC-2026-CP21-UNITREE-GO2-VOLUME-COMMAND at CVE-2026-115995, description and vendor ticket 474. New evidence concerns the bounded reported mechanism, prerequisite or outcome; setting research_demonstration; exploit status not_established; remediation status patch_available. No independently comparable impact scale, affected production population or universal exploit success measure was established, so the impact band remains null. Original Claims remain individually attributable and any observed incident or simulated result is distinguished in the narrative.

Assessed Oct 27, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

Timeline

  1. Oct 24, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-ENRICH-20261027-37The Unitree Go2 advisory attributes OS command injection to the chat_go gpt_thread.py set_volume Value argument, lists releases through 1.1.11.4 as affected, and identifies 1.1.11.5 as the vendor fix.supported

Basis: reported finding

Link to claim
CLM-CP21-UNITREE-GO2-VOLUME-COMMAND-1The GitHub advisory describes attacker-influenced set_volume values reaching a shell in the Go2 chat software, lists affected releases up to 1.1.11.4 and names 1.1.11.5 as fixed.supported

Basis: reported finding

Link to claim

Implications

Language-driven physical interfaces need to keep user-facing slot values separate from process control and actuator permission.

Controls and mitigations

  • Update to verified fixed firmware and invoke volume control through fixed APIs or argument arrays with bounded integer input, not through a shell-interpolated string.

Unknowns and contradictions

  • The listing is an advisory rather than an independently observed intrusion; callers, firmware variation, process identity, and any ability to affect locomotion are not fully established.

Sources and citation

Material revision history

  1. Oct 27, 2026 · Canonical change recorded · new in release · revision 196