On this page (7 sections)
Ubuntu published USN-9115-1 on 17 November 2026, covering three vulnerabilities in Mini-XML (also called mxml), a small C library for reading and writing XML. Two of them can crash a program through runaway recursion. The third is a stack-based buffer overflow that Ubuntu says could, in the worst case, allow arbitrary code execution.
If you run Ubuntu 16.04 LTS or 18.04 LTS servers, especially ones that process XML files from outside sources, check whether the libmxml1 package is installed and whether the fixed version is available to you. The fixes are delivered through Ubuntu Pro (ESM), not the standard archive.
What Ubuntu fixed
Mini-XML is a library, not a service. It does nothing by itself, but any program linked against it inherits its bugs when that program opens or writes XML. Ubuntu describes the overall risk as Mini-XML being made to crash or run programs if it opened a specially crafted file.
| CVE | Weakness | Impact (per Ubuntu / NVD) | CVSS (NVD) |
|---|---|---|---|
| CVE-2016-4570 | CWE-400, uncontrolled resource consumption in mxmlDelete | Crash and denial of service through stack consumption | 5.5 Medium |
| CVE-2016-4571 | CWE-400, uncontrolled resource consumption in mxml_write_node | Crash and denial of service through stack consumption | 5.5 Medium |
| CVE-2018-20004 | CWE-787, out-of-bounds write in mxml_write_node | Crash, or possibly arbitrary code execution | 8.8 High |
Technical details in plain terms
Unbounded recursion (CVE-2016-4570 and CVE-2016-4571)
Ubuntu explains that Mini-XML used unbounded recursion when deleting and writing XML nodes. A deeply nested XML document makes the library call itself over and over until the stack is used up, and the process crashes. The CVE-2016-4570 advisory concerns the mxmlDelete function and the CVE-2016-4571 advisory concerns mxml_write_node. Both were published in the NVD on 3 February 2017 and list mxml 2.9 and 2.7, and possibly earlier versions. Ubuntu states these two only affected 16.04 LTS.
Stack buffer overflow (CVE-2018-20004)
The third issue is more serious. Per the GitHub advisory, a stack-based buffer overflow exists in mxml_write_node in mxml 2.12, involving a double-precision floating point number. Ubuntu words it as the library incorrectly handling certain floating point values when writing XML nodes. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, meaning network reachable, low complexity, no privileges, but user interaction required. Ubuntu says an attacker could possibly cause a crash or possibly execute arbitrary code.
The CVE references include public write-ups tagged as exploit material, including an upstream issue tracker entry. Public details exist, but the research does not report any attacks in the wild. The FIRST EPSS estimates shown by GitHub are about 1.6% for the two 2016 CVEs and about 2.0% for CVE-2018-20004 over the next 30 days. That is a probability estimate, not evidence of exploitation.
Who is realistically exposed
Exposure depends on whether a program on your system uses libmxml1 and feeds it XML you do not fully control. A few practical points:
- The affected releases are Ubuntu 16.04 LTS and 18.04 LTS. Both are past standard support, so fixes come through Ubuntu Pro with ESM Apps.
- The two recursion bugs matter mostly for availability: a crafted file can crash the program that parses it.
- The overflow matters most where an application writes XML containing attacker-influenced numeric values, or opens files from untrusted users, uploads or third parties.
- Systems that have libmxml1 installed only as an unused dependency carry less practical risk, but the package should still be updated.
- The research does not list which applications link to Mini-XML, so check your own systems instead of assuming.
How to check your servers
Start by finding out whether the library is installed and which version you have. The first command is read-only and lists the installed libmxml1 package and its version. Run it on each Ubuntu 16.04 and 18.04 host.
dpkg -l libmxml1Compare the result with the fixed versions: 2.10-1ubuntu0.1~esm1 on 18.04 LTS and 2.9-0ubuntu2+esm1 on 16.04 LTS. If you see an older version, the system is not yet patched. To see which installed packages depend on the library, run this read-only query. It lists the packages that would be affected by a crash or exploit through Mini-XML.
apt-cache rdepends --installed libmxml1If this prints nothing beyond the header, no installed package depends on the library through the package manager. Software you compiled yourself or bundled in an application directory will not appear here, so check vendor-supplied applications separately.
What to do now
- Inventory every Ubuntu 16.04 and 18.04 host and run dpkg -l libmxml1 to see whether the package is present.
- Confirm the host has Ubuntu Pro with ESM Apps enabled, since the fixes are delivered that way. Ubuntu notes Pro is free for up to five machines.
- Run the package update and confirm the version matches the fixed one for your release.
- Restart services that use the library so they load the patched version (see the warning below).
- If you cannot patch right away, stop accepting XML files from untrusted sources in any application that uses Mini-XML, and limit who can submit files to it.
- Plan an upgrade off 16.04 and 18.04. Relying on extended maintenance is a stopgap, not a long-term position.
On a host with ESM Apps enabled, a standard update pulls the fix. This command refreshes package lists and upgrades only libmxml1. Afterward, rerun dpkg -l libmxml1 and look for the fixed version string.
sudo apt update && sudo apt install --only-upgrade libmxml1Monitoring afterwards
Library bugs like these tend to show up as application crashes first. Watch for unexplained restarts or segmentation faults in services that parse XML, and for unusually large or deeply nested files arriving at upload or import endpoints. A repeated crash right after a file is processed deserves a look even if the cause is not yet known.
For public-facing sites, regular outside-in checks help catch what changes after an incident. Webforta Monitor tracks uptime, certificate, DNS and header changes, which can reveal a service that keeps falling over. For general hygiene on exposed servers, the small business website security guide covers patching habits, and what to do if your website is hacked is worth having ready if a crash turns out to be more than a crash.
Bottom line
USN-9115-1 is a patch-and-restart job rather than an emergency. Nothing in the research indicates active exploitation, but CVE-2018-20004 is a memory corruption bug with public technical details, and the affected Ubuntu releases are old ones where fixes only arrive through ESM. Find the hosts, apply the update, restart the dependent services, and use the opportunity to schedule a move to a supported release.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
