CVE-2026-116017: xinnan-tech xiaozhi-esp32-server

Affected products, as the CNA wrote them
Vendor	Product	Versions
xinnan-tech	xiaozhi-esp32-server pkg:github/xinnan-tech/xiaozhi-esp32-server	affected before 0.9.8 semver Other versions: unaffected

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
5.3	Medium	4.0	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	CNA (VulnCheck)Used for this record
4.3	Medium	3.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N	CNA (VulnCheck)

CISA KEV Not listed.
EPSS 0.0023, the 13th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 24 Oct 2026. New records show when each source confirmed them.

Sources

References from the CNA

github.com/xinnan-tech/xiaozhi-esp32-server/issues/3459 issue-tracking
github.com/xinnan-tech/xiaozhi-esp32-server/pull/3460 patchissue-tracking
github.com/xinnan-tech/xiaozhi-esp32-server/commit/d4ff9c5c17cbd82ec98a2a6bb4f82a07c1be0f03 patch
github.com/xinnan-tech/xiaozhi-esp32-server/releases/tag/v0.9.8 release-notes
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 technical-description
github.com/xinnan-tech/xiaozhi-esp32-server/blob/v0.9.7/main/manager-api/src/main/resources/mapper/device/DeviceAddressBookDao.xml#L5-L10 technical-description
hackmd.io/@hieuPenguinnn/xiaozhi-esp32-server-address-book-idor third-party-advisory
www.vulncheck.com/advisories/xiaozhi-esp32-server-before-0.9.8-idor-via-device-address-book-endpoint third-party-advisory

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.