# CVE-2026-116017: Xiaozhi-esp32-server before 0.9.8 IDOR via device address-book endpoint


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-2hv3-q586-pf3c

## What is CVE-2026-116017?

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

### Official description

Xiaozhi-esp32-server before 0.9.8 contains an insecure direct object reference vulnerability in the manager-api DeviceController.getAddressBook handler that allows authenticated users to read other users' device address books. Attackers with a normal or self-registered account can request /device/address-book/{macAddress} with another user's device MAC to obtain contact MACs, aliases, call permissions, and owner user IDs.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-116017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116017 is a medium-severity vulnerability in xinnan-tech xiaozhi-esp32-server, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116017 in the wild and no public exploit code.

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

## Sources

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

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