# CVE-2026-112094: michaelrsweet mxml mxml-file.c mxml_load_data use after free

> A use-after-free vulnerability in the mxml library allows remote attackers to potentially execute code or cause denial of service via crafted input.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112094, GHSA-2m37-39hv-427w, UBUNTU-CVE-2026-112094

## What is CVE-2026-112094?

CVE-2026-112094 is a medium-severity use after free vulnerability in michaelrsweet mxml, published on 19 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-112094?


## How do I fix CVE-2026-112094?

No fix published yet.

## Is CVE-2026-112094 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112094 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112094 and fix it if it is affected.

What it is: CVE-2026-112094 is a medium-severity use after free vulnerability in michaelrsweet mxml, published on 19 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112094 exists.

Affected product: michaelrsweet mxml. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112094/ (Markdown: https://insights.sbomify.com/CVE-2026-112094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112094
- OSV: https://osv.dev/vulnerability/CVE-2026-112094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112094/
Summaries are generated and may contain mistakes; the official description above is the record.