# CVE-2026-110604: Mini-XML 4.0.0 through 4.0.6 Stack Out-of-Bounds Write via mxml_strtod()

> Attackers can trigger a stack out-of-bounds write in Mini-XML by supplying crafted XML with specific locale settings, potentially causing crashes or code execution.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110604, GHSA-pc2v-ppxx-vfq5, UBUNTU-CVE-2026-110604

## What is CVE-2026-110604?

CVE-2026-110604 is a low-severity memory corruption vulnerability in Michael R Sweet Mini-XML, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Mini-XML 4.0.0 through 4.0.6 contains an off-by-one stack out-of-bounds write in mxml_strtod() when the locale decimal point is not '.'. Attackers can supply XML with a 63-digit REAL value followed by '.' to write a NUL byte past the 64-byte stack buffer, corrupting stack memory or crashing the process.

Weakness: CWE-193 (Off-by-one Error)

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


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

Apply the vendor's patch.

## Is CVE-2026-110604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110604 is a low-severity memory corruption vulnerability in Michael R Sweet Mini-XML, published on 14 Oct 2026. It can only be exploited from the same machine or local 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-110604 exists.

Affected product: Michael R Sweet Mini-XML. 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-110604/ (Markdown: https://insights.sbomify.com/CVE-2026-110604/index.md)
```

## Sources

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

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