# CVE-2026-111136: libInstPatch through 1.1.7 Heap Out-of-Bounds Write via ipatch_sf2_gen_is_valid

> Attackers can execute arbitrary code or cause denial of service via crafted SoundFont files exploiting a heap out-of-bounds write in libInstPatch.

- **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:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111136, ECHO-e2bb-3785-63b6, GHSA-6p4q-22pq-927g, UBUNTU-CVE-2026-111136, openSUSE-SU-2026:12199-1

## What is CVE-2026-111136?

CVE-2026-111136 is a medium-severity memory corruption vulnerability in swami libinstpatch, published on 15 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

libInstPatch through 1.1.7 contains a heap out-of-bounds write vulnerability in the SoundFont 2 loader because ipatch_sf2_gen_is_valid() does not range-check generator IDs before the validity mask test. Attackers can supply crafted SF2 files with out-of-range pgen or igen generator IDs to write attacker-chosen values past the zone genarray, corrupting heap memory and crashing Swami or other consumers.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libinstpatch` | openSUSE:Tumbleweed | All versions | 1.1.8-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-111136 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111136 is a medium-severity memory corruption vulnerability in swami libinstpatch, published on 15 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-111136 exists.

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

## Sources

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

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