Skip to main content
← Vulnerabilities

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).

Only affects dr_libs 0.14.5 applications that call drwav_init_with_metadata, drwav_init_file_with_metadata, or drwav_init_memory_with_metadata on untrusted WAV files. No fix is listed in the available facts.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects dr_libs version 0.14.5 Application uses dr_wav metadata-reading init functions on an untrusted WAV file

Published
Last modified
Reference
Last checked
26/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

The dr_wav component of dr_libs contains an out-of-bounds write flaw in its CUE metadata handling. A remote attacker without login can trigger it by providing a specially crafted .wav file that a user must open.

Read the original description

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.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Affects dr_libs version 0.14.5 Application uses dr_wav metadata-reading init functions on an untrusted WAV file
  • Workaround: The facts list no fix. Until one is available, limit the risk by avoiding the drwav_init_*_with_metadata functions when reading untrusted WAV files.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-11316 (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).), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-11316 (entry last updated 2026-11-10):
Affected:
- mackron dr_libs: versions 0.14.5
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects dr_libs version 0.14.5 (source: https://talosintelligence.com/vulnerability_reports/TALOS-2026-2442)
- Application uses dr_wav metadata-reading init functions on an untrusted WAV file (source: https://talosintelligence.com/vulnerability_reports/TALOS-2026-2442)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-11316 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-11316 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://talosintelligence.com/vulnerability_reports/TALOS-2026-2442
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-11316
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-11316.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • mackron dr_libs

    0.14.5

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-11316

Is CVE-2026-11316 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The bug is an out-of-bounds write in the CUE metadata reading code of dr_wav. Sanitizer runs confirm an attacker could cause a write to an attacker-influenced address with an attacker-controlled value, and the crash is a memory-safety fault.Source: talosintelligence.com

Which versions are affected by CVE-2026-11316?

dr_libs: version 0.14.5.Source: cve.now feed data

Am I affected, and how do I check?

The affected version is dr_libs 0.14.5. The issue applies to applications that call drwav_init_with_metadata, drwav_init_file_with_metadata, or drwav_init_memory_with_metadata on an untrusted WAV file. To check, look at the dr_libs version in use and search the code for those function calls.Source: talosintelligence.com

How do I fix CVE-2026-11316?

The available facts do not name a fixed version or an upgrade target, so no specific upgrade can be recommended from them. Review where those metadata init functions are called with untrusted WAV input.Source: talosintelligence.com

What if there's no patch?

The facts list no fix. Until one is available, limit the risk by avoiding the drwav_init_*_with_metadata functions when reading untrusted WAV files.Source: talosintelligence.com