# CVE-2026-92879: vgmstream mus_acm.c parse_mus resource consumption

> Remote attackers can cause resource exhaustion in vgmstream via crafted MUS files, leading to denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/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:** 17 Sep 2026
- **Also known as:** GHSA-8r6v-wgrg-22rc

## What is CVE-2026-92879?

CVE-2026-92879 is a medium-severity denial of service 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 security flaw has been discovered in vgmstream up to r2117. This issue affects the function parse_mus of the file src/meta/mus_acm.c. The manipulation results in resource consumption. The attack may be launched remotely. The patch is identified as ae37662ad626254ddd96ad69ac263792d7a92024. Applying a patch is advised to resolve this issue.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-92879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92879 is a medium-severity denial of service 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-92879 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-92879/ (Markdown: https://insights.sbomify.com/CVE-2026-92879/index.md)
```

## Sources

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

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