Quick answers
- Is CVE-2026-92879 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92879 being exploited in the wild.
- How severe is CVE-2026-92879?
- Medium severity, with a CVSS score of 4.3, published 17 September 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-92879?
- A patch was published on 2026-08-23: Patch commit ae37662ad626254ddd96ad69ac263792d7a92024 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92879 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92879?
- Check whether you run Vgmstream at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a resource exhaustion / denial of service flaw in the parse_mus function within src/meta/mus_acm.c of vgmstream up to revision r2117. The issue involves improper buffer and integer handling that can lead to unbounded resource consumption when processing specially-crafted MUS audio files. The attack requires network delivery of a malicious file and user interaction to open it, but no authentication is required. An attacker can cause a denial of service by exhausting CPU or memory resources. The patch (commit ae37662ad626254ddd96ad69ac263792d7a92024) addresses buffer overflow and integer overflow issues in the parsing logic.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-09-17: disclosed
- 2026-08-23: patched: Patch commit ae37662ad626254ddd96ad69ac263792d7a92024