# CVE-2026-92880: vgmstream EA SCHl parser vadpcm_decoder.c vadpcm_read_coefs_be out-of-bounds write

> An out-of-bounds write in the EA SCHl parser allows remote attackers to execute arbitrary code or cause denial of service via crafted audio files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-4fcx-9cr4-72mc

## What is CVE-2026-92880?

CVE-2026-92880 is a medium-severity memory corruption vulnerability in vgmstream, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in vgmstream up to r2117. Impacted is the function vadpcm_read_coefs_be of the file src/coding/vadpcm_decoder.c of the component EA SCHl parser. This manipulation of the argument entry/entries causes out-of-bounds write. Remote exploitation of the attack is possible. Patch name: ae37662ad626254ddd96ad69ac263792d7a92024. It is suggested to install a patch to address this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-92880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92880 is a medium-severity memory corruption vulnerability in vgmstream, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92880 in the wild and no public exploit code.

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

## Sources

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

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