Menu

Star on GitHub · 3.2k

CVE-2025-58146

There are multiple issues.

Published Jul 9, 2026CWE-20EPSS 0.18%

Overview

CVE-2025-58146 is a known-severity vulnerability. It was published on July 9, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-58146?

CVE-2025-58146 is a known-severity vulnerability. It was published on July 9, 2026.

How severe is CVE-2025-58146?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-58146?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-58146?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-58146 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.