Quick answers
- Is CVE-2026-92880 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92880 being exploited in the wild.
- How severe is CVE-2026-92880?
- Medium severity, with a CVSS score of 6.3, published 17 September 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-92880?
- A patch was published on 2026-08-23: Fix committed as ae37662ad626254ddd96ad69ac263792d7a92024 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92880 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92880?
- 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 an out-of-bounds write flaw in the vadpcm_read_coefs_be function within the EA SCHl parser component of vgmstream (affecting versions up to r2117). The vulnerable code in src/coding/vadpcm_decoder.c improperly validates or bounds-checks function arguments before writing to a buffer, allowing an attacker-controlled input to write beyond allocated memory. Remote exploitation is possible by providing a crafted audio file that triggers the buffer overflow. The patch (commit ae37662ad626254ddd96ad69ac263792d7a92024) addresses buffer and integer overflow issues in the parsing logic. Users should update vgmstream to a version that includes this commit or later.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-09-17: disclosed
- 2026-08-23: patched: Fix committed as ae37662ad626254ddd96ad69ac263792d7a92024