# CVE-2026-52297: Memory corruption in FFmpeg

> An out-of-bounds read in FFmpeg's MOV parsing allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-52297, GHSA-vp63-fqg3-cph4, UBUNTU-CVE-2026-52297

## What is CVE-2026-52297?

CVE-2026-52297 is a low-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FFmpeg before 9.0 has an out-of-bounds read because there is insufficiently padded extradata in the MOV parsing path in mov_read_iacb in libavformat/mov.c.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2026-52297 being exploited?

There is no known exploitation of CVE-2026-52297 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-52297 and fix it if it is affected.

What it is: CVE-2026-52297 is a low-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52297 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-52297/ (Markdown: https://insights.sbomify.com/CVE-2026-52297/index.md)
```

## Sources

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

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