# CVE-2026-112007: Schism Tracker through 20260524 Heap Out-of-Bounds Write via ULT Loader

> Attackers can execute arbitrary code or crash Schism Tracker by providing a crafted .ult module that triggers a heap out-of-bounds write.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/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:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112007, GHSA-qfh4-g83h-4vcx, UBUNTU-CVE-2026-112007

## What is CVE-2026-112007?

CVE-2026-112007 is a medium-severity memory corruption vulnerability in schismtracker Schism Tracker, published on 18 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

Schism Tracker through 20260524 contains a heap out-of-bounds write vulnerability in fmt_ult_load_song() in fmt/ult.c that fails to clamp the one-byte sample count to MAX_SAMPLES. Attackers can supply a crafted .ult module that overwrites the instruments pointer array, causing csf_destroy() to free attacker-chosen pointers and crash the application.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

No fix has been published for CVE-2026-112007 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112007 is a medium-severity memory corruption vulnerability in schismtracker Schism Tracker, published on 18 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-112007 exists.

Affected product: schismtracker Schism Tracker. 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-112007/ (Markdown: https://insights.sbomify.com/CVE-2026-112007/index.md)
```

## Sources

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

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