# CVE-2026-107697: FFmpeg before 8.1.3 HLS Demuxer Security Check Bypass via parse_playlist()

> Attackers can bypass HLS security restrictions to access disallowed protocols or local files via crafted playlists in FFmpeg.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/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:** 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-107697, ECHO-a1b6-5fc7-f6ea, GHSA-hhvh-2vr7-77mx, MINI-jgq2-r8rc-x5xm, UBUNTU-CVE-2026-107697

## What is CVE-2026-107697?

CVE-2026-107697 is a medium-severity 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 a protection mechanism failure in the HLS demuxer that allows attackers to bypass protocol and allowed_extensions restrictions when opening child playlists. Attackers can supply a crafted master playlist whose child playlists use disallowed protocols or non-multimedia local files, making parse_playlist() open resources the HLS security policy should block.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2026-107697 being exploited?

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

What it is: CVE-2026-107697 is a medium-severity 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: There is no known exploitation of CVE-2026-107697 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-107697/ (Markdown: https://insights.sbomify.com/CVE-2026-107697/index.md)
```

## Sources

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

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