# CVE-2026-115995: Unitree Robotics Unitree Go2 chat_go gpt_thread.py set_volume os command injection


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hr6g-r3r7-8h6f

## What is CVE-2026-115995?

CVE-2026-115995 is a critical vulnerability in Unitree Go2, published on 24 Oct 2026. 

### Official description

A security vulnerability has been detected in Unitree Robotics Unitree Go2 up to 1.1.11.4. The impacted element is the function set_volume of the file gpt_thread.py of the component chat_go. Such manipulation of the argument Value leads to os command injection. The attack can be launched remotely. Upgrading to version 1.1.11.5 is sufficient to resolve this issue. You should upgrade the affected component. The vendor confirmed early: "Submission 990502 corresponds to our internal ticket #474 (Go2 chat_go set_volume OS command injection, CWE-78)."

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-115995?


## How do I fix CVE-2026-115995?

No fix has been published for CVE-2026-115995 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115995 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115995 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115995 and fix it if it is affected.

What it is: CVE-2026-115995 is a critical vulnerability in Unitree Go2, published on 24 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115995 exists.

Affected product: Unitree Go2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115995/ (Markdown: https://insights.sbomify.com/CVE-2026-115995/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115995
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115995
- OSV: https://osv.dev/vulnerability/CVE-2026-115995

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115995/
Summaries are generated and may contain mistakes; the official description above is the record.