# CVE-2026-71261: dr_wav.h W64 CUE Chunk Metadata Parsing Integer Overflow Leading to Heap Buffer Overflow on 32-bit Builds

> Integer overflow in dr_wav.h W64 CUE chunk parsing on 32-bit builds leads to heap buffer overflow, potentially allowing code execution or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-cfw7-vmp5-wg69, UBUNTU-CVE-2026-71261

## What is CVE-2026-71261?

CVE-2026-71261 is a high-severity vulnerability in mackron dr_libs, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

dr_libs dr_wav.h (all versions through current master) contains an integer overflow in W64 CUE chunk metadata parsing. In drwav__metadata_process_chunk, a stage-1 capacity estimate truncates the 64-bit W64 chunk sizeInBytes to size_t before dividing by DRWAV_CUE_POINT_BYTES; on 32-bit builds this truncation causes the pre-allocated extra metadata capacity to be computed incorrectly.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-71261?


## How do I fix CVE-2026-71261?

No fix has been published for CVE-2026-71261 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71261 being exploited?

There is no known exploitation of CVE-2026-71261 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71261 and fix it if it is affected.

What it is: CVE-2026-71261 is a high-severity vulnerability in mackron dr_libs, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71261 in the wild and no public exploit code.

Affected product: mackron dr_libs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71261/ (Markdown: https://insights.sbomify.com/CVE-2026-71261/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71261
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71261
- OSV: https://osv.dev/vulnerability/CVE-2026-71261

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71261/
Summaries are generated and may contain mistakes; the official description above is the record.