Home

Description

There are multiple issues. 1. Updates to the XAPI database sanitise input strings, but try generating the notification using the unsanitised input. This causes the database's event thread to terminate and cease further processing. 2. XAPI's UTF-8 encoder implements v3.0 of the Unicode spec, but XAPI uses libraries which conform to the stricter v3.1 of the Unicode spec. This causes some strings to be accepted as valid UTF-8 by XAPI, but rejected by other libraries in use. Notably, such strings can be entered into the database, after which the database can no longer be loaded. 3. There is no input sanitisation for Map/Set updates on objects in the XAPI database.

PUBLISHED Reserved 2025-08-26 | Published 2026-07-09 | Updated 2026-07-09 | Assigner XEN




CRITICAL: 9.4CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Problem types

CWE-20 Improper input validation

Product status

Default status
unaffected

all
affected

Credits

This issue was discovered by Edwin Török from XenServer. finder

References

www.openwall.com/lists/oss-security/2025/09/09/3

xenbits.xen.org/xsa/advisory-474.html

xenbits.xen.org/xsa/advisory-474.html

cve.org (CVE-2025-58146)

nvd.nist.gov (CVE-2025-58146)

Download JSON