# CVE-2026-116727: gbsplay through 0.0.103 Heap Out-of-Bounds Read via vgm_open in gbs.c


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-f826-v6gp-c5xh, UBUNTU-CVE-2026-116727

## What is CVE-2026-116727?

CVE-2026-116727 is a medium-severity vulnerability in mmitch gbsplay, published on 26 Oct 2026. 

### Official description

gbsplay through 0.0.103 contains a heap out-of-bounds read vulnerability in vgm_open() in gbs.c that walks the VGM command stream without bounds checks. Attackers can supply a crafted VGM file with wait opcodes and no 0x66 terminator to read past the heap buffer and crash the player.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-116727 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116727 is a medium-severity vulnerability in mmitch gbsplay, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116727 in the wild and no public exploit code.

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

## Sources

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

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