Quick answers
- Is CVE-2026-86514 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86514 being exploited in the wild.
- How severe is CVE-2026-86514?
- Medium severity, with a CVSS score of 6.3, published 8 September 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-86514?
- A patch was published on 2026-07-11: Patch commit 4669d37a6af94866f6f0628678f9f90d46954e8b Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86514 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86514?
- 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
A stack-based buffer overflow exists in the sscanf function call within src/meta/txth.c of vgmstream up to revision r2117, affecting the txth-txtp component. The vulnerability is caused by improper bounds checking when parsing txth format metadata, allowing an attacker to overflow stack buffers. The attack requires only the ability to provide a malicious txth file to an application using vgmstream; no authentication is required. Exploitation could lead to denial of service or arbitrary code execution. The vulnerability was patched in commit 4669d37a6af94866f6f0628678f9f90d46954e8b, which added proper buffer size constraints to sscanf format specifiers.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-09-08: disclosed
- 2026-07-11: patched: Patch commit 4669d37a6af94866f6f0628678f9f90d46954e8b