CVE-2025-58146

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.

CVSS

No CVSS.

References

Link	Resource
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

Configurations

No configuration.

History

No history.

Information

Published : 2026-07-09 16:16

Updated : 2026-07-09 17:16

NVD link : CVE-2025-58146

Mitre link : CVE-2025-58146

CVE.ORG link : CVE-2025-58146

JSON object : View

Products Affected

No product.

CWE

CWE-20

Improper Input Validation

{"id": "CVE-2025-58146", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-58146", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-09T16:07:50.376243Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security@xen.org", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.4, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security@xen.org", "affectedData": [{"vendor": "Xen", "product": "XAPI", "versions": [{"status": "affected", "version": "all"}], "platforms": ["Linux"], "defaultStatus": "unaffected"}]}], "published": "2026-07-09T16:16:33.687", "references": [{"url": "https://xenbits.xen.org/xsa/advisory-474.html", "source": "security@xen.org"}, {"url": "http://www.openwall.com/lists/oss-security/2025/09/09/3", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://xenbits.xen.org/xsa/advisory-474.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@xen.org", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "There are multiple issues.\n\n 1. Updates to the XAPI database sanitise input strings, but try\n generating the notification using the unsanitised input. This\n causes the database's event thread to terminate and cease further\n processing.\n\n 2. XAPI's UTF-8 encoder implements v3.0 of the Unicode spec, but XAPI\n uses libraries which conform to the stricter v3.1 of the Unicode\n spec. This causes some strings to be accepted as valid UTF-8 by\n XAPI, but rejected by other libraries in use. Notably, such strings\n can be entered into the database, after which the database can no\n longer be loaded.\n\n 3. There is no input sanitisation for Map/Set updates on objects in the\n XAPI database."}], "lastModified": "2026-07-09T17:16:56.657", "sourceIdentifier": "security@xen.org"}