vgmstream CVE-2026-110660

Requires a victim to open or let a vgmstream-based application process an attacker-supplied .s14 or .sss (Siren14/G.722.1) file; the flaw triggers specifically during format detection when decode_vector_quantized_mlt_indices() is reached and the bit reader refills without bounds-checking the data_u32 array end. LIMITING FACTORS: this is a LOCAL vector (AV:L) requiring passive user interaction (UI:P) - the attacker cannot trigger it without the victim handling the file - and impact is limited to an application crash (availability only), with no confidentiality or integrity effect. No special non-default configuration is needed; any vgmstream build through r2117 that parses the crafted file is affected.

Signals are consistent and point to a low-to-moderate, availability-only issue rather than a top priority. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L) scores 4.8 and describes a local attack requiring passive user interaction (the victim must open or process a malicious file), with impact limited to the vulnerable system's availability (VA:L) and NO confidentiality or integrity impact. This is corroborated by the description, which states the OOB read results in 'crashing the application' - i.e., a denial-of-service/crash, not data exfiltration. Publicly available exploit code exists (a HackMD write-up is referenced), which raises practical reproducibility, but there is NO CISA KEV listing and NO active-exploitation evidence, so exploitation status is 'publicly available exploit code exists' only. No EPSS score and no SSVC decision were provided in the input, so probabilistic and decision-framework signals cannot be weighed. CONFLICT TO NOTE: the input Tag 'Information Disclosure' is inconsistent with the CVSS vector (VC:N) and the description (crash), so this should be treated as a crash/DoS primitive, not a confirmed information leak - verify before escalating. Net: real but low priority given the local vector, required user interaction, and crash-only impact.

An attacker crafts a malicious .s14 or .sss Siren14/G.722.1 audio file and distributes it (e.g., bundled with a game audio rip or shared on a forum). When a victim opens or lets a vgmstream-based application auto-scan the file, format detection invokes the G.722.1 decoder whose unchecked bit-reader refill reads past the stack buffer, crashing the application. A public proof-of-concept write-up exists, so reproduction is straightforward, but impact is limited to a local denial of service.