CVE-2026-116017
Received Received - Intake

Xiaozhi-ESP32-Server Insecure Direct Object Reference in Device Address Book

Vulnerability report for CVE-2026-116017, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-24

Last updated on: 2026-10-24

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-24
Last Modified
2026-10-24
Generated
2026-10-24
AI Q&A
2026-10-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
xinnan-tech xiaozhi-esp32-server 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-116017 is an Insecure Direct Object Reference (IDOR) vulnerability in the xiaozhi-esp32-server's manager-api module. It allows authenticated users to access other users' device address books by exploiting a missing ownership check in the GET /device/address-book/{macAddress} endpoint. The endpoint does not verify if the requested device belongs to the user, enabling attackers to read sensitive data like contact MACs, aliases, call permissions, and owner user IDs.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthorized requests to /device/address-book/{macAddress} endpoints with MAC addresses not owned by the requesting user. Check server logs for repeated access attempts to address book endpoints with varying MAC addresses. Use tools like curl to test if the endpoint returns data for arbitrary MACs: curl -X GET http://<server>/device/address-book/<target_mac> -H 'Authorization: Bearer <token>'

Verify if version 0.9.8 or later is installed by checking the server version endpoint or release notes. If running 0.9.7 or earlier, the system is vulnerable.

Impact Analysis

This vulnerability allows attackers with a normal or self-registered account to access other users' device address books. They can obtain sensitive information such as contact MAC addresses, aliases, call permissions, and owner user IDs. Additionally, attackers can wipe another user's address book by sending a POST /device/unbind request with another user's device UUID due to lack of ownership verification.

Mitigation Strategies

Immediately upgrade to version 0.9.8 or later to address the IDOR vulnerability and related issues. Ensure device ownership validation is enforced in all address book operations before and after upgrade.

Review and restrict user permissions, especially for self-registered accounts. Implement additional logging and monitoring for address book access attempts to detect exploitation attempts.

If immediate upgrade is not possible, implement network-level controls to block unauthorized access to /device/address-book endpoints until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116017. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart