# CVE-2026-119703: xiaozhi-esp32-server through 0.9.8 Authentication Bypass via Spoofed Device-ID Header


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-wv6h-fhj6-j53g

## What is CVE-2026-119703?

CVE-2026-119703 is a medium-severity vulnerability in xinnan-tech xiaozhi-esp32-server, published on 30 Oct 2026. 

### Official description

xiaozhi-esp32-server through 0.9.8 contains an authentication bypass vulnerability in WebSocketServer._handle_auth that allows remote unauthenticated attackers to skip Bearer HMAC token verification by spoofing the Device-ID header. Attackers supplying an allowlisted MAC-address-shaped device identifier can open an authenticated WebSocket session, issue voice-assistant commands, exchange audio, and read that device's conversation context.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-119703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119703 is a medium-severity vulnerability in xinnan-tech xiaozhi-esp32-server, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119703 exists.

Affected product: xinnan-tech xiaozhi-esp32-server. 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-119703/ (Markdown: https://insights.sbomify.com/CVE-2026-119703/index.md)
```

## Sources

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

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