Rust advisories / wasapi
UnsoundRUSTSEC-2026-0332 · wasapi
RUSTSEC-2026-0332: `WaveFormat::parse` reads past the end of a `&WAVEFORMATEX`
Short answerwasapi has an API that can cause undefined behaviour from safe code: `WaveFormat::parse` reads past the end of a `&WAVEFORMATEX`. Fixed in 0.25.0.
| Crate | wasapi |
|---|---|
| Type | Unsound (memory-exposure) |
| Affected versions | From 0.20.0 before 0.25.0. |
| Fixed in | 0.25.0 |
| Severity | not scored |
| Published | 2026-09-08 |
| Last changed | 2026-10-07 |
| Also known as | none |
| Affected functions | wasapi::WaveFormat::parse |
What to do
- See which version you have:
cargo tree -i wasapi(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p wasapi. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplewasapi = "0.25.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
WaveFormat::parse is a safe function that takes a &WAVEFORMATEX, which is only valid for reads of size_of::<WAVEFORMATEX>() (18) bytes. When the header has wFormatTag == WAVE_FORMAT_EXTENSIBLE and cbSize >= 22, the function reinterprets the reference as a WAVEFORMATEXTENSIBLE and reads 40 bytes. Nothing in the signature guarantees that the header sits at the start of a larger buffer, so safe code can trigger an out-of-bounds read:
use wasapi::WaveFormat;
use windows::Win32::Media::Audio::WAVEFORMATEX;
use windows::Win32::Media::KernelStreaming::WAVE_FORMAT_EXTENSIBLE;
let header = WAVEFORMATEX {
wFormatTag: WAVE_FORMAT_EXTENSIBLE as u16,
nChannels: 2,
nSamplesPerSec: 48000,
nAvgBytesPerSec: 384000,
nBlockAlign: 8,
wBitsPerSample: 32,
cbSize: 22,
};
// Reads 22 bytes past the end of `header`.
let _ = WaveFormat::parse(&header);
A more likely way to hit this is to copy the header out of a format pointer returned by WASAPI (let fmt = unsafe { *ptr };) and pass &fmt. The copy keeps cbSize, but not the 22 bytes that follow it. The bytes read past the end are returned as the channel mask and subformat of the parsed format.
The flaw was corrected in commit 2562db7, released in 0.25.0. parse is now an unsafe fn that takes a *const WAVEFORMATEX, and the caller must guarantee that the pointer is valid for reads of size_of::<WAVEFORMATEX>() + cbSize bytes. WaveFormat::parse_from_blob_bytes (available since 0.23.0) is the safe alternative and checks the slice length against cbSize.
References
- Package: crates.io/crates/wasapi
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0332.html
- Report: github.com/HEnquist/wasapi-rs/issues/65
- Web: github.com/HEnquist/wasapi-rs/pull/64
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?