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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

`WaveFormat::parse` is a safe function that takes a `&WAVEFORMATEX`, which is only valid for reads of `size_of:: ()` (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: ```rust 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…

Published by the source

8 Sep 2026, 12:00 UTC

Last modified by the source

7 Oct 2026, 14:45 UTC

Source last checked

23 Oct 2026, 22:04 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record RUSTSEC-2026-0332

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: rustsec-2026-0332

Advisory: `WaveFormat::parse` reads past the end of a `&WAVEFORMATEX`
IDs: rustsec-2026-0332
Record: https://patchnext.com/advisories/rustsec-2026-0332 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wasapi 0.25.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io wasapi: affected >= 0.20.0, < 0.25.0; fixed in 0.25.0

## Suggested inspection (read-only)
- crates.io wasapi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wasapi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0332 (OSV record RUSTSEC-2026-0332 lists affected ranges: crates.io wasapi >=0.20.0 <0.25.0 (fixed))

Commands are suggestions: review each one before running it.