# CVE-2026-107677: FFmpeg through 9.0.2 DASH Demuxer Infinite Loop via Empty SegmentTemplate Media

> Attackers can cause a denial of service in FFmpeg by providing a crafted DASH manifest with an empty segment template, leading to an infinite loop.

- **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:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107677, ECHO-7475-7be3-3d40, GHSA-23w5-87r9-849m, UBUNTU-CVE-2026-107677

## What is CVE-2026-107677?

CVE-2026-107677 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 denial of service vulnerability in the DASH demuxer that allows attackers to trigger an infinite loop by supplying an empty SegmentTemplate media URL. Attackers can craft an .mpd manifest declaring SegmentTemplate media="" so get_current_fragment() calls av_strireplace() with an empty search string, consuming CPU indefinitely.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2026-107677 being exploited?

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

What it is: CVE-2026-107677 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-107677 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-107677/ (Markdown: https://insights.sbomify.com/CVE-2026-107677/index.md)
```

## Sources

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

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