Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-88385 Overview
CVE-2026-88385 is a memory leak vulnerability in Mini-XML 4.0.5, a lightweight C-based XML parsing library. The flaw resides in the mxml_load_data() function during parsing of malformed XML input. Text nodes allocated by mxmlNewText() can become unlinked from the parent tree before a parse error transfers control to the cleanup path. The orphaned nodes are never released, producing a persistent memory leak with each parsing attempt. Attackers who can submit repeated crafted XML inputs can exhaust process memory and trigger denial of service in applications linking Mini-XML.
Critical Impact
Repeated parsing of attacker-controlled malformed XML causes cumulative memory exhaustion, leading to denial of service in any service that embeds Mini-XML 4.0.5.
Affected Products
- Mini-XML version 4.0.5
- Applications and services statically or dynamically linking the vulnerable Mini-XML build
- Downstream distributions packaging Mini-XML 4.0.5
Discovery Timeline
- 2026-09-24 - CVE-2026-88385 published to the National Vulnerability Database
- 2026-09-24 - Last updated in NVD database
Technical Details for CVE-2026-88385
Vulnerability Analysis
Mini-XML is a small XML parsing library maintained by Michael R Sweet and widely embedded in printing stacks, embedded systems, and C/C++ utilities. The vulnerability affects mxml_load_data(), the central parsing routine in mxml-file.c. During parsing, the function allocates text nodes using mxmlNewText() and attaches them to a parent node. When specific malformed input triggers an error after allocation but before the node is properly linked, control jumps to the cleanup error label. The cleanup logic walks the parent tree to free nodes, but orphaned nodes outside the tree remain allocated for the lifetime of the process.
Services that call Mini-XML repeatedly, such as configuration loaders, IPC endpoints, or print subsystems, leak heap memory on every malformed request. Over time this exhausts available memory and forces the process to terminate or become unresponsive. The vulnerability class is a Memory Leak leading to Denial of Service through Resource Exhaustion.
Root Cause
The root cause is missing validation of the parent pointer before adding a value node. When parent is NULL, the allocated text node has no owner, so the error path cannot reach it through tree traversal. The patch adds an explicit parent check and jumps to the error handler before the allocation is orphaned.
Attack Vector
An attacker supplies malformed XML to any application that calls mxmlLoadString(), mxmlLoadFile(), or related entry points. Each parse attempt leaks heap memory. Repeated submissions, which may be unauthenticated depending on the host application, result in progressive memory exhaustion.
// Add a new value node...
*bufptr = '\0';
+ if (!parent)
+ {
+ // Can't have a value node without a parent...
+ _mxml_error(options, "Value cannot be a root node on line %d.", line);
+ goto error;
+ }
+
switch (type)
{
case MXML_TYPE_INTEGER :
Source: GitHub commit 83ef80ae3c5413b73f501edb59ee74e31ce399d0
Detection Methods for CVE-2026-88385
Indicators of Compromise
- Steady increase in resident set size (RSS) of processes that embed Mini-XML, with no corresponding workload growth
- Repeated parser error log entries referencing malformed XML or _mxml_error output
- Out-of-memory kills (OOM killer events) targeting services that process untrusted XML
Detection Strategies
- Inventory binaries and packages linking libmxml or statically compiled Mini-XML 4.0.5 using software composition analysis tools
- Instrument long-running XML-consuming services with memory profilers such as Valgrind or heaptrack to confirm cumulative growth under malformed input
- Correlate application crash telemetry with spikes in inbound XML payloads flagged as invalid
Monitoring Recommendations
- Alert on sustained memory growth of parser processes beyond expected baselines
- Monitor rate of XML parse failures per source address to detect automated abuse
- Track process restarts and OOM events across hosts running affected services
How to Mitigate CVE-2026-88385
Immediate Actions Required
- Identify every application that bundles Mini-XML 4.0.5 and prioritize internet-facing services for remediation
- Apply the upstream patch commit 83ef80ae3c5413b73f501edb59ee74e31ce399d0 or upgrade to a fixed release once available
- Restart affected services after patching to clear previously leaked memory
Patch Information
The fix is published in the Mini-XML repository as commit 83ef80ae3c5413b73f501edb59ee74e31ce399d0, which adds a parent null-check in mxml_load_data() and routes the error through the cleanup path before allocating an orphan node. Issue tracking and discussion are available in GitHub Issue #356. Rebuild dependent binaries after applying the patch.
Workarounds
- Place XML-consuming services behind a reverse proxy or input filter that rejects malformed XML before it reaches the parser
- Enforce size and rate limits on inbound XML payloads to slow memory exhaustion
- Run affected processes under resource controls such as systemdMemoryMax or cgroup limits with automated restart on OOM
# Example systemd hardening for an affected service
[Service]
MemoryMax=512M
Restart=on-failure
RestartSec=5s
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

