Skip to main content
VulnerabilityPublished

CVE-2026-92879: vgmstream · Resource Consumption

Affects vgmstreamSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% 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:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 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 1 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 official patch identified by commit ae37662ad626254ddd96ad69ac263792d7a92024 to resolve this vulnerability. No other mitigation guidance is provided. Since the patch is available, updating to the fixed version is the recommended action.

Description

A security flaw has been discovered in vgmstream up to r2117. This issue affects the function parse_mus of the file src/meta/mus_acm.c. The manipulation results in resource consumption. The attack may be launched remotely. The patch is identified as ae37662ad626254ddd96ad69ac263792d7a92024. Applying a patch is advised to resolve this issue.

References

Community reviews

Loading reviews…