CVE-2025-58146 Details
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.
A vulnerability in Xen's XAPI component allows for denial-of-service conditions through improper input handling. XAPI's UTF-8 encoder, which follows version 3.0 of the Unicode specification, can accept certain strings as valid UTF-8 that are rejected by other libraries conforming to the stricter version 3.1. This discrepancy can be exploited by guest administrators, leading to the introduction of malformed strings into the XAPI database. Once these strings are entered, they cause the database to become unreadable, disrupting normal operations. Additionally, there is a separate issue where updates to the XAPI database do not properly sanitize input strings before processing, causing the database's event thread to crash and halt further operations. This advisory also notes a lack of input sanitization for Map/Set updates on objects within the XAPI database, a vulnerability that can only be exploited by authenticated API users.
To address this vulnerability, an updated version of XAPI should be deployed, incorporating the patch available as part of this advisory. After applying the patch, XAPI can be restarted. If the restart is successful, no further action is needed. However, if malformed strings have been introduced into the database, they must be manually removed before XAPI can function properly. This can be done by stopping the XAPI service, backing up the database, using a command to strip bad characters from the database file, and then restarting the XAPI service.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jul 9, 2026CISA-ADP
Assessed Jul 9, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| http://www.openwall.com/lists/oss-security/2025/09/09/3 | CVE | AdvisoryMailing ListRemedy |
| http://xenbits.xen.org/xsa/advisory-474.html | CVE | AdvisoryRemedyVendor |
| https://xenbits.xen.org/xsa/advisory-474.html | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-20 | Improper Input Validation | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Xen | < 2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 9, 2026 | CVE Modified | CISA-ADP |
| Jul 9, 2026 | New CVE Received | [email protected] |
| Jul 9, 2026 | CVE Modified | CVE |
Volerion