# CVE-2026-4009: jarikomppa soloud WAV File dr_wav.h drwav_read_pcm_frames_s16__msadpcm out-of-bounds

> A local attacker can trigger an out-of-bounds read in the Soloud audio library's WAV parser, potentially causing crashes or leaking memory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-wg5p-6g8f-jr88

## What is CVE-2026-4009?

CVE-2026-4009 is a medium-severity memory corruption vulnerability in jarikomppa soloud, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in jarikomppa soloud up to 20200207. Impacted is the function drwav_read_pcm_frames_s16__msadpcm in the library src/audiosource/wav/dr_wav.h of the component WAV File Parser. The manipulation leads to out-of-bounds read. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. Upgrading to version 20200207 is recommended to address this issue. It is recommended to upgrade the affected component. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-4009?


## How do I fix CVE-2026-4009?

No fix has been published for CVE-2026-4009 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4009 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4009 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4009 and fix it if it is affected.

What it is: CVE-2026-4009 is a medium-severity memory corruption vulnerability in jarikomppa soloud, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4009 exists.

Affected product: jarikomppa soloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4009/ (Markdown: https://insights.sbomify.com/CVE-2026-4009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4009
- OSV: https://osv.dev/vulnerability/CVE-2026-4009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4009/
Summaries are generated and may contain mistakes; the official description above is the record.
