# CVE-2026-107678: FFmpeg through 9.0.2 Stack Exhaustion via Recursive Free of pssh Boxes

> Attackers can crash FFmpeg and cause high CPU usage by providing a crafted MP4 file with excessive pssh boxes, affecting applications using the library.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/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:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107678, ECHO-4c92-12ce-a2f9, GHSA-rp4v-7m3g-89vg, UBUNTU-CVE-2026-107678

## What is CVE-2026-107678?

CVE-2026-107678 is a medium-severity denial of service 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 a stack exhaustion vulnerability in av_encryption_init_info_free() in libavutil/encryption_info.c, which recursively frees AVEncryptionInitInfo linked lists built by the MOV demuxer's mov_read_pssh(). Attackers can supply a crafted MP4 file with tens of thousands of small pssh boxes to exhaust the stack and crash the process, while also causing quadratic CPU consumption.

Weakness: CWE-674 (Uncontrolled Recursion)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

No fix has been published for CVE-2026-107678 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107678 being exploited?

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

What it is: CVE-2026-107678 is a medium-severity denial of service 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-107678 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-107678/ (Markdown: https://insights.sbomify.com/CVE-2026-107678/index.md)
```

## Sources

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

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