Quick answers
- Is CVE-2026-105249 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105249 being exploited in the wild.
- How severe is CVE-2026-105249?
- Medium severity, with a CVSS score of 4.8, published 5 October 2026.
- Which products and versions are affected?
- Vgmstream up to r2117.
- Is there a fix for CVE-2026-105249?
- Yes: fixed in r2118 or later (commit ae37662ad626254ddd96ad69ac263792d7a92024 onwards). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105249 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-105249?
- 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 or later (commit ae37662ad626254ddd96ad69ac263792d7a92024 onwards)
Technical details
A use-after-free vulnerability exists in the make_group_random function within src/meta/txtp_process.c, the TXTP file handler component of vgmstream. The flaw can be exploited via a locally crafted TXTP file. The vulnerability is fixed in commit ae37662ad626254ddd96ad69ac263792d7a92024, which addresses buffer and overflow issues.
Affected products
- vgmstream vgmstream up to r2117
Timeline
- 2026-10-05: disclosed