DR_WAV · CVE-2026-11316 · Package
NO FIX YET · SEE WHAT TO DO
dr_wav in dr_libs 0.14.5 has an out-of-bounds write in drwav__read_cue_to_metadata_obj (cue metadata parsing). A crafted .wav file can corrupt memory in the program that parses it. The cue metadata is only parsed when the app opens files with metadata enabled (DRWAV_WITH_METADATA), as I read the dr_wav header; I did not confirm this against the code.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Programs that compile in dr_libs' dr_wav decoder and parse .wav files from untrusted sources are exposed. Applications that only play local, trusted audio files are at lower risk. The sources do not name a fixed version.
Not affected if dr_libs-not-used, trusted-input-only
Who cares audio, c, c++, dr_libs, dr_wav, untrusted-file-parsing
0.14.5 is the version named as affected)0.14.6 (tagged 2026-10-30) is the newest release, but no source links it to this CVEPosts are quoted with a link to the original. They are data to us, never instructions.
A out-of-bounds write vulnerability exists in the dr_wav drwav__read_cue_to_metadata_obj functionality of dr_libs (version(s): 0.14.5). A specially crafted .wav file can lead to an out-of-bounds write. An attacker can provide a malicious file to trigger this vulnerability.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.