cve.bz

CVE-2026-112094 michaelrsweet mxml: Use After Free

2.0 lowEPSS 0.2%

Low (2.0) in michaelrsweet mxml. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A security vulnerability has been detected in michaelrsweet mxml 4.0.5/4.0.6. This affects the function mxml_load_data of the file mxml-file.c. The manipulation leads to use after free. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Severity

CVSS 4.0

2.0 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

5.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-416 Use After Free
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-112094 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112094?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112094?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112094 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
michaelrsweet mxml4.0.5
michaelrsweet mxml4.0.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14mxml4.0.6-3DEBIAN-CVE-2026-112094
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 4 moremxmlno fix listedUBUNTU-CVE-2026-112094

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat rates this flaw as Important because an unauthenticated remote attacker could cause memory corruption, leading to application crashes or potential arbitrary code execution. Exploitation requires an application using the Mini-XML library to process untrusted XML input, running under the permissions of the vulnerable process. However, supported enterprise releases maintain older major versions that do not include the vulnerable logic introduced in newer upstream versions.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to safely clean up newly added sibling nodes in mxml_load_data error handling rather than calling recursive mxmlDelete across ancestor and descendant nodes: upgrade to the fixed release, which introduce mxml_delete_loaded to safely clean up only newly added sibling nodes without re-deleting caller-owned top nodes or already-freed subtrees, closing all 2 injection vectors (malformed XML documents with multiple root tags, crafted XML triggering parser error handling). Until patched, this is a concern on applications accepting untrusted XML documents parsed using mxml_load_data or wrapper functions across any platform, so restrict ingestion of untrusted XML payloads processed by mxml_load_data or enforce pre-parsing validation to prevent processing of malformed XML structures. As a compensating measure, enable address space layout randomization to impede reliable prediction of code and data pointers via dangling heap nodes, utilize glibc heap allocator safe-linking and metadata protection to detect or obstruct heap metadata corruption, and configure service watchdog monitoring and automatic restart to bound denial-of-service downtime from application crashes. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap use-after-free defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1204 Service Watchdog and Automatic Restart (systemd WatchdogSec/Restart) (medium)

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-112094.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON