---
id: CVE-2025-58146
title: |-
  There are multiple issues.

   1
summary: |-
  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
      pro…
severity: none
cwe:
  - CWE-20
published: '2026-07-09'
updated: '2026-09-29'
sourceUpdated: '2026-09-29T19:10:00.160'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-58146'
references:
  - url: 'https://xenbits.xen.org/xsa/advisory-474.html'
    label: security@xen.org
  - url: 'http://www.openwall.com/lists/oss-security/2025/09/09/3'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'http://xenbits.xen.org/xsa/advisory-474.html'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
epss: 0.00178
epssPercentile: 0.06601
ingestedAt: '2026-09-29T19:44:04.105Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.