CVE-2025-58146
XAPI UTF-8 string handling
- State
- Published
- Severity
- 9.4 Critical
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Reserved
- Aug 26, 2025
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 9.4 Critical | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H | XEN |
Weaknesses
- CWE-20 Improper input validation
Affected Products
| Product | Versions |
|---|---|
XAPIXen |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.