# CVE-2026-107676: FFmpeg through 9.0.2 Uninitialized Memory Disclosure via HDR10+ Metadata Serializer

> Attackers can leak process memory into output files by crafting specific metadata in media files processed by FFmpeg.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/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:** 8 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107676, ECHO-568a-c122-8733, GHSA-77pg-jq65-mg2f, UBUNTU-CVE-2026-107676

## What is CVE-2026-107676?

CVE-2026-107676 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 8 Oct 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

FFmpeg through 9.0.2 contains an uninitialized memory disclosure vulnerability in av_dynamic_hdr_plus_to_t35() that leaves up to three payload bytes uninitialized when tone_mapping_flag is 0. Attackers can supply crafted Matroska T.35 BlockAdditional or HEVC/AV1 SEI metadata so that remuxing or transcoding writes leaked process memory into output files.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2026-107676 being exploited?

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

What it is: CVE-2026-107676 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 8 Oct 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-107676 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-107676/ (Markdown: https://insights.sbomify.com/CVE-2026-107676/index.md)
```

## Sources

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

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