Quick answers
- Is CVE-2026-105250 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105250 being exploited in the wild.
- How severe is CVE-2026-105250?
- Medium severity, with a CVSS score of 4.3, published 5 October 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-105250?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-105250 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105250?
- 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 decode_ms_ima() function in src/coding/ima_decoder.c fails to validate frame_channels and block_samples before using them in arithmetic operations, particularly a modulo operation. An attacker can craft a RIFF/WAVE file with malformed header fields to force invalid decoder geometry (non-positive channel or block sample counts) that trigger the divide-by-zero condition when the decoder processes the file.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-08-20: disclosed
- 2026-10-05: advisory