# CVE-2026-64835: FFmpeg 4.4 - 8.1.2 Out-of-Bounds Memory Access in ADX Audio Decoder

> Attackers can trigger out-of-bounds memory access in FFmpeg's ADX decoder via crafted audio files, potentially leading to code execution or crashes.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-64835, ECHO-8b20-d6e3-e563, GHSA-p2v8-4c4f-rwpq, JLSEC-2026-1177, MINI-gh6x-w3f4-qm2r, UBUNTU-CVE-2026-64835

## What is CVE-2026-64835?

CVE-2026-64835 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FFmpeg versions 4.4 through 8.1.2 contain an out-of-bounds memory access vulnerability in the ADX audio decoder within libavcodec/adxdec.c that allows attackers to trigger both out-of-bounds reads and writes by supplying a crafted ADX or AAX audio file with a mid-stream channel layout change. When AV_PKT_DATA_NEW_EXTRADATA side data is received mid-stream, the adx_decode_frame function re-parses the stream header but fails to update the internal channel state, causing subsequent decoding operations to access the prev[] state array using a stale channel count.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2026-64835 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64835 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-64835 in the wild and no public exploit code.

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

## Sources

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

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