# CVE-2026-96674: alsa-lib through 1.2.16.1 Integer Overflow via Topology File

> Attackers can cause integer overflows in alsa-lib via crafted topology files, leading to out-of-bounds reads that may leak sensitive data or crash the application.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** AZL-105054, DEBIAN-CVE-2026-96674, ECHO-21cd-b9f7-14b1, GHSA-w2qj-qh9f-h5cc, UBUNTU-CVE-2026-96674

## What is CVE-2026-96674?

CVE-2026-96674 is a medium-severity vulnerability in alsa-lib, published on 23 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

alsa-lib through 1.2.16.1 computes combined topology element size using 32-bit arithmetic in src/topology/ctl.c, allowing integer overflow that defeats bounds checks. Attackers can supply crafted topology files that wrap size calculations, causing the decoder to read beyond the topology buffer and potentially leak sensitive data or crash the application.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-96674 being exploited?

There is no known exploitation of CVE-2026-96674 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96674 is a medium-severity vulnerability in alsa-lib, published on 23 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: There is no known exploitation of CVE-2026-96674 in the wild and no public exploit code.

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

## Sources

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

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