Quick answers
- Is CVE-2026-109828 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109828 being exploited in the wild.
- How severe is CVE-2026-109828?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Libsndfile up to 1.2.2.
- Is there a fix for CVE-2026-109828?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-109828 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-109828?
- 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 wavlike_subchunk_parse function in src/wavlike.c fails to initialize variables before use when parsing short 'labl' subchunks in WAV files, leading to use of uninitialized stack memory (CWE-457). Remote exploitation is possible through a crafted WAV file; no authentication or user interaction beyond opening the file is required. An attacker gains the ability to read uninitialized stack memory.
Affected products
- libsndfile libsndfile up to 1.2.2
Timeline
- 2026-10-13: disclosed