# CVE-2026-110660: vgmstream through r2117 Stack Out-of-Bounds Read via G.722.1/Siren14 Decoder


- **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:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gvx8-xp47-575f

## What is CVE-2026-110660?

CVE-2026-110660 is a medium-severity vulnerability in vgmstream, published on 14 Oct 2026. 

### Official description

vgmstream through r2117 contains a stack out-of-bounds read vulnerability in the G.722.1/Siren14 decoder in g7221_lib.c, whose bit reader refills without checking the data_u32 array end. Attackers can supply crafted .s14 or .sss files that drive decode_vector_quantized_mlt_indices() past the stack buffer during format detection, crashing the application.

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

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


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

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

## Is CVE-2026-110660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110660 is a medium-severity vulnerability in vgmstream, published on 14 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110660 exists.

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

## Sources

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

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