CVE-2026-4009
Out-of-Bounds Read in jarikomppa soloud WAV File Parser
Publication date: 2026-03-12
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jarikomppa | soloud | to 20200207 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-4009 is an out-of-bounds read vulnerability found in the jarikomppa soloud audio library, specifically in the function drwav_read_pcm_frames_s16__msadpcm within the WAV File Parser component (src/audiosource/wav/dr_wav.h).
This vulnerability occurs when the function reads memory beyond the intended buffer boundaries, either before or after the buffer, which can lead to unexpected behavior or crashes.
The issue requires local access to exploit and is considered easy to exploit, with a public proof-of-concept exploit available.
Upgrading to version 20200207 of soloud is recommended to fix this vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability impact me? :
This vulnerability can impact the availability of the affected system by causing crashes due to out-of-bounds memory reads.
Additionally, it may expose sensitive memory content when processing maliciously crafted WAV files, posing a security risk.
Since the attack requires local access, an attacker must have some level of access to the system to exploit it.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by reproducing the out-of-bounds read condition locally on the affected system. Since the exploit requires local access and involves processing a specially crafted MSADPCM WAV file, detection involves running a test harness with AddressSanitizer (ASan) enabled to catch invalid memory reads.
Suggested detection steps include building the SoLoud audio library and a provided test harness with ASan enabled, then running the harness with a malicious WAV file designed to trigger the vulnerability. The ASan report will indicate an invalid read if the vulnerability is present.
- Build SoLoud with ASan: `clang -fsanitize=address -g -o test_harness test_harness.c -lsoLoud` (example command)
- Run the test harness with the crafted WAV file: `./test_harness malicious.wav`
Monitoring system logs or crash reports for AddressSanitizer errors related to `drwav_read_pcm_frames_s16__msadpcm` can also help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary and recommended mitigation step is to upgrade the affected SoLoud audio library to version 20200207 or later, where this vulnerability has been fixed.
Since the attack requires local access, restricting local user permissions and limiting access to systems running vulnerable versions can reduce risk.
Avoid processing untrusted or malicious MSADPCM WAV files until the upgrade is applied.