dr_libs dr_wav.h version 0.14.4 and earlier (fixed in commit 8a7258c) contain a heap buffer overflow vulnerability in the drwav__read_smpl_to_metadata_obj() function of dr_wav.h that allows memory corruption via crafted WAV files. Attackers can exploit a mismatch between sampleLoopCount validation in pass 1 and unconditional processing in pass 2 to overflow heap allocations with 36 bytes of attacker-controlled data through any drwav_init_*_with_metadata() call on untrusted input.
Security readout for executives and security teams
Plain-English summary
CVE-2026-29022 is a high-severity memory corruption flaw in the dr_wav.h audio parser. Software that embeds affected dr_libs code and opens untrusted WAV files could crash or corrupt memory when processing crafted metadata. The bundle does not show active exploitation, but the attack path is realistic for file-handling applications.
Executive priority
Prioritize remediation for software that accepts WAV files from users, partners, or the internet. This is not proven actively exploited in the provided sources, but memory corruption in file parsers can affect availability and integrity and is often hard to detect after deployment.
Technical view
dr_wav.h 0.14.4 and earlier contain a heap buffer overflow in drwav__read_smpl_to_metadata_obj(). Sources describe inconsistent sampleLoopCount handling between metadata sizing and processing passes, allowing crafted WAV metadata to overflow heap allocations through drwav_init_*_with_metadata() on untrusted input.
Likely exposure
Exposure is most likely in products that vendor dr_wav.h directly and parse user-supplied WAV files with metadata enabled. Header-only library copies may be missed by normal dependency inventory. Network exposure depends on the embedding application, such as upload, conversion, media, or desktop file-open workflows.
Exploitation context
The CVSS vector requires local interaction and user action, consistent with opening or processing a malicious WAV file. The source bundle marks KEV as false and provides no evidence of active exploitation. One reference is tagged exploit, so proof-of-concept details may exist publicly.
Researcher notes
The key condition is metadata parsing of crafted smpl chunks. Sources attribute the overflow to pass-one validation not matching pass-two processing. Validate exposure by source review and patched commit comparison. Do not assume all dr_libs consumers are affected unless they include the vulnerable header and reachable metadata APIs.
Mitigation direction
Update vendored dr_wav.h to commit 8a7258c or later vendor guidance.
Audit all embedded or copied dr_libs headers, not only package manifests.
Avoid metadata parsing for untrusted WAV files until patched.
Sandbox audio parsing paths and enforce resource limits where feasible.
Add regression coverage for malformed WAV metadata handling.
Validation and detection
Locate every dr_wav.h copy and identify its upstream version or commit.
Confirm patched copies include commit 8a7258cc66b49387ad58cc5b81568982a3560d49.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.