CVE-2025-58146
CriticalCVSS 9.4Summary
Multiple issues exist in XAPI: (1) database updates sanitize input strings but generate notifications from unsanitized input, causing the database event thread to terminate; (2) XAPI's UTF-8 encoder implements Unicode v3.0 while libraries use v3.1, leading to acceptance of invalid strings that can prevent database loading; (3) no input sanitization for Map/Set updates on database objects.
Risk Assessment
Risk includes disruption of XAPI database operations, leading to service unavailability, and potential insertion of invalid data that prevents database loading, causing permanent loss of functionality.
Recommendation
Immediately update XAPI to a patched version, implement additional input validation mechanisms, and ensure UTF-8 encoding compatibility with all libraries in use.
Original NVD description (English source)
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.