# CVE-2026-107695: FFmpeg before 8.1.3 HLS Demuxer Infinite Loop via Self-Referencing Playlist

> Remote attackers can cause denial of service in FFmpeg by tricking users into opening a crafted self-referencing HLS playlist, leading to infinite loops and resource exhaustion.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** Over the internet
- **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-107695, ECHO-477e-8137-8531, GHSA-wrmh-p2hh-7cf6, MINI-94gx-m9vp-87qj, UBUNTU-CVE-2026-107695

## What is CVE-2026-107695?

CVE-2026-107695 is a high-severity denial of service vulnerability in Ffmpeg Ffmpeg, published on 8 Oct 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 before 8.1.3 contains an infinite loop vulnerability in the HLS demuxer that allows remote attackers to cause denial of service because parse_playlist() accepts Master Playlist tags inside Media Playlists. Attackers can trick victims into opening a crafted self-referencing playlist that endlessly adds variants in hls_read_header(), causing unbounded CPU and I/O consumption.

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

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2026-107695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107695 exists.

## 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-107695 and fix it if it is affected.

What it is: CVE-2026-107695 is a high-severity denial of service vulnerability in Ffmpeg Ffmpeg, published on 8 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107695 exists.

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

## Sources

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

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