Advisory record · RUSTSEC-2026-0332

`WaveFormat::parse` reads past the end of a `&WAVEFORMATEX`

No CVSS score

Published by OSV at 8 Sept 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasapicrates.io>=0.20.0, <0.25.00.25.0
Identifiers
RUSTSEC-2026-0332
Published
8 Sept 2026
Updated
7 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions 0.20.0 up to but not including 0.25.0 of the wasapi crate are affected. In these versions, the WaveFormat::parse function can read 22 bytes past the end of a WAVEFORMATEX header when the header is a WAVE_FORMAT_EXTENSIBLE format with cbSize of at least 22, and this can be reached from safe code, such as by copying a header out of a WASAPI format pointer and passing a reference to it. Upgrade to wasapi 0.25.0 or later. Code that cannot upgrade can use WaveFormat::parse_from_blob_bytes, available since 0.23.0, which checks the slice length against cbSize.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.