Skip to main content
VulnerabilityPublished

CVE-2026-105248: vgmstream · Out-of-bounds Write

Affects vgmstreamSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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

A patch identified by commit 4669d37a6af94866f6f0628678f9f90d46954e8b is available and should be applied to affected versions of vgmstream to remediate this vulnerability. Applying this official fix is the recommended mitigation.

Description

A security flaw has been discovered in vgmstream up to r2117. This affects the function parse_params/txtp_parse of the file src/meta/txtp_parser.c of the component TXTP File Handler. The manipulation results in out-of-bounds write. The attack may be launched remotely. The patch is identified as 4669d37a6af94866f6f0628678f9f90d46954e8b. It is best practice to apply a patch to resolve this issue.

References

Community reviews

Loading reviews…