Vulnerability 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.
Related Weaknesses (CWE)
References
- https://xenbits.xen.org/xsa/advisory-474.html
- http://www.openwall.com/lists/oss-security/2025/09/09/3
- http://xenbits.xen.org/xsa/advisory-474.html
FAQ
What is CVE-2025-58146?
CVE-2025-58146 is a documented vulnerability. 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 t...
How severe is CVE-2025-58146?
CVSS scoring is not yet available for CVE-2025-58146. Check NVD for updates.
Is there a patch for CVE-2025-58146?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.