# CVE-2026-88386: Memory corruption in n/a

> A misaligned memory access in libsndfile allows attackers to cause a denial of service via crafted WAV files.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** AZL-106800, DEBIAN-CVE-2026-88386, ECHO-9923-e474-207e, GHSA-x44m-83p2-j4h6, OESA-2026-4561, OESA-2026-4562, OESA-2026-4563, OESA-2026-4564, UBUNTU-CVE-2026-88386, openSUSE-SU-2026:12142-1

## What is CVE-2026-88386?

CVE-2026-88386 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

libsndfile 1.2.2 contains a misaligned memory access issue in psf_binheader_readf() while parsing WAV fmt chunks. A specially crafted WAV file can cause the function to cast an unaligned destination address to unsigned int * and perform a 4-byte store. This results in undefined behavior leading to denial of service.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsndfile` | openSUSE:Tumbleweed | All versions | 1.2.2-6.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-88386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88386 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88386 exists.

Affected product: n/a. 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-88386/ (Markdown: https://insights.sbomify.com/CVE-2026-88386/index.md)
```

## Sources

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

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