Quick answers
- Is CVE-2026-88386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88386 being exploited in the wild.
- How severe is CVE-2026-88386?
- Medium severity, with a CVSS score of 5.5, published 24 September 2026.
- Which products and versions are affected?
- Libsndfile 1.2.2.
- Is there a fix for CVE-2026-88386?
- A patch was published on 2026-09-01: Fix committed via memcpy-based approach Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88386 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-88386?
- Check whether you run Libsndfile at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a misaligned memory access in psf_binheader_readf() when parsing WAV fmt chunks with wFormatTag 0x0055 (MPEG Layer 3). The function casts a potentially unaligned pointer to unsigned int* and performs 4-byte stores, which is undefined behavior per the C standard. On strict-alignment architectures (ARM, RISC-V, SPARC) or with UBSan enabled, this causes a bus error or SIGILL, leading to denial of service; x86 may tolerate the misaligned access.
Affected products
- libsndfile libsndfile 1.2.2
Timeline
- 2026-08-05: disclosed: Issue #1150 opened on GitHub
- 2026-09-24: advisory: CVE-2026-88386 published
- 2026-09-01: patched: Fix committed via memcpy-based approach