Quick answers
- Is CVE-2026-105251 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105251 being exploited in the wild.
- How severe is CVE-2026-105251?
- Medium severity, with a CVSS score of 6.3, published 5 October 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-105251?
- Yes: fixed in r2118 and later (patch 4b8316652a30d40f99ad43310bed273fd1f8a7a3). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105251 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105251?
- 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.
How to fix
- Fixed in: r2118 and later (patch 4b8316652a30d40f99ad43310bed273fd1f8a7a3)
Technical details
An out-of-bounds read vulnerability exists in the ps_find_padding function of psx_decoder.c, which handles PlayStation Audio (VAG) format files. The function fails to validate that sufficient data is available before reading a full frame, allowing an attacker to supply a crafted or truncated VAG file that triggers a read past the allocated buffer. The attack requires no authentication or user interaction beyond opening a malicious audio file.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-10-05: disclosed
- 2026-10-05: patched: Patch merged as commit 4b8316652a30d40f99ad43310bed273fd1f8a7a3