Skip to main content
VulnerabilityPublished Updated

CVE-2026-105249: vgmstream · Use After Free

Affects vgmstreamSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.4 Low.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.4Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
vgmstreamAffected
  • =r2117
Fixed in–
GitHubvgmstream/vgmstreampkg:github/vgmstream/vgmstreamOther threatsAffected
  • =r2117
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:vgmstream:vgmstream:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the patch identified by commit ae37662ad626254ddd96ad69ac263792d7a92024 to remediate this use-after-free vulnerability. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-105249 is a use-after-free vulnerability in the vgmstream software up to version r2117. It affects the make_group_random function in the src/meta/txtp_process.c file, specifically within the TXTP File Handler component. The vulnerability requires local access to exploit and has a low severity score. A patch identified by commit ae37662ad626254ddd96ad69ac263792d7a92024 is recommended to fix this issue.

References

Community reviews

Loading reviews…