# CVE-2026-105837: libmikmod before 3.3.14 Heap Buffer Overflow via DSM Loader Integer Overflow

> Attackers can trigger heap buffer overflow and potential code execution in libmikmod via crafted DSM files exploiting an integer overflow.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-106664, DEBIAN-CVE-2026-105837, GHSA-rr6f-2vgw-5v76, UBUNTU-CVE-2026-105837

## What is CVE-2026-105837?

CVE-2026-105837 is a high-severity vulnerability in sezero libmikmod, published on 6 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

libmikmod before 3.3.14 contains an integer overflow vulnerability in DSM_Load() in load_dsm.c that allows attackers to trigger heap buffer overflow via crafted track counts. Attackers can supply a DSM module whose numchn and numpat product wraps a 16-bit value, overwriting heap memory to cause crashes or potential code execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Upgrade to a fixed version.

## Is CVE-2026-105837 being exploited?

There is no known exploitation of CVE-2026-105837 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105837 is a high-severity vulnerability in sezero libmikmod, published on 6 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: There is no known exploitation of CVE-2026-105837 in the wild and no public exploit code.

Affected product: sezero libmikmod. 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-105837/ (Markdown: https://insights.sbomify.com/CVE-2026-105837/index.md)
```

## Sources

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

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