CVE-2026-110660 vgmstream CVE debrief

Who should care

Defenders responsible for systems or applications using vgmstream through r2117 should assess exposure and prioritize verification and potential remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who handle multimedia files. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

Defenders should care about CVE-2026-110660 because it affects vgmstream through r2117, potentially allowing crafted files to cause application crashes. Roles responsible for system and application security, particularly those handling multimedia files, should assess exposure and prioritize verification and remediation efforts.

• Potential application crashes or instability
• Need for verification of affected versions and remediation
• Possible denial-of-service (DoS) scenarios
• Importance of input validation and error handling for .s14 and .sss files

Technical summary

The vulnerability exists in the G.722.1/Siren14 decoder in g7221_lib.c, where the bit reader refills without checking the data_u32 array end. This can be exploited by supplying crafted .s14 or .sss files that drive decode_vector_quantized_mlt_indices() past the stack buffer during format detection, crashing the application. The affected product is vgmstream through r2117, and defenders should prioritize verifying the affected version and applying patches or mitigations as available. The vulnerability has a CVSS score of 4.8 and a severity of MEDIUM.

Defensive priority

Defenders should prioritize verifying the affected version of vgmstream and applying patches or mitigations as available.

Recommended defensive actions

• Verify the version of vgmstream in use and check for patches or updates
• Implement input validation and error handling for .s14 and .sss file processing
• Monitor for and restrict suspicious .s14 and .sss file uploads or processing
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its existence in vgmstream through r2117 and the potential for a crash. However, there is limited information on exploitation, impact, or remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.