Application crash via unterminated BEXT coding history
Published Mar 17, 2026 · Updated Mar 17, 2026
Heap out-of-bounds read in the WAV BEXT metadata parser in miniaudio 0.11.25 and earlier allows attackers to crash applications. The ma_dr_wav__read_bext_to_metadata_obj function reserves a terminator byte but leaves it unwritten before ma_dr_wav__strlen scans the heap without a bound. Exploitation requires an application to parse a crafted WAV file with metadata enabled and interrupts that application through a memory-access crash.
Summary
What happened
Heap out-of-bounds read in the WAV BEXT metadata parser in miniaudio 0.11.25 and earlier allows attackers to crash applications. The ma_dr_wav__read_bext_to_metadata_obj function reserves a terminator byte but leaves it unwritten before ma_dr_wav__strlen scans the heap without a bound. Exploitation requires an application to parse a crafted WAV file with metadata enabled and interrupts that application through a memory-access crash.
The record
- CVE
- CVE-2026-32837
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- miniaudio
- Product
- miniaudio
- Classifications
- CWE-170, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.11.25
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- BEXT coding-history crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo