Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, the ast_xml_open() function in xml.c parses XML documents using libxml with unsafe parsing options that enable entity expansion and XInclude processing. Specifically, it invokes xmlReadFile() with the XML_PARSE_NOENT flag and later processes XIncludes via xmlXIncludeProcess().If any untrusted or user-supplied XML file is passed to this function, it can allow an attacker to trigger XML External Entity (XXE) or XInclude-based local file disclosure, potentially exposing sensitive files from the host system. This can also be triggered in other cases in which the user is able to supply input in xml format that triggers the asterisk process to parse it. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.
This vulnerability carries a LOW severity rating with a CVSS v3.1 score of 2.0, indicating it can be exploited remotely over the network but requires specific conditions to be met though user interaction is required . The vulnerability impacts limited integrity, for affected systems. Impacting 2 products from sangoma, from sangoma organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-02-06T17:16:26.147
2026-02-18T18:42:37.300
Analyzed
CVSSv3.1: 2.0 (LOW)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | sangoma | asterisk | < 20.18.2 | Yes |
| Application | sangoma | asterisk | < 21.12.1 | Yes |
| Application | sangoma | asterisk | < 22.8.2 | Yes |
| Application | sangoma | asterisk | < 23.2.2 | Yes |
| Application | sangoma | certified_asterisk | ≤ 18.9 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For sangoma's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.