# CVE-2026-115996: Unitree Robotics Unitree Go2 chat_go websocket.py WebSocketClient.connect certificate validation


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-c3qh-x7xm-9m28

## What is CVE-2026-115996?

CVE-2026-115996 is a medium-severity vulnerability in Unitree Go2, published on 24 Oct 2026. 

### Official description

A vulnerability was detected in Unitree Robotics Unitree Go2 up to 1.1.13/1.1.14.1/1.1.15.1. This affects the function WebSocketClient.connect of the file websocket.py of the component chat_go. Performing a manipulation results in improper certificate validation. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is reported as difficult. The vendor confirmed early: "These issues were previously submitted by the researcher through our Security Response Center platform and are tracked internally as follows: Submission 990504 corresponds to our internal ticket #616 (Go2 chat_go WSS client disabled TLS server certificate validation, CWE-295)."

Weakness: CWE-295 (Improper Certificate Validation), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-115996 being exploited?

There is no known exploitation of CVE-2026-115996 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115996 is a medium-severity vulnerability in Unitree Go2, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115996 in the wild and no public exploit code.

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-115996/ (Markdown: https://insights.sbomify.com/CVE-2026-115996/index.md)
```

## Sources

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

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