# CVE-2023-6601: Ffmpeg: hls unsafe file extension bypass in ffmpeg

> Attackers can bypass file extension checks in FFmpeg's HLS demuxer using base64 data URIs to trigger arbitrary demuxers, potentially leading to code execution.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A: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:** 6 Jan 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-6601, GHSA-wj7r-cv36-mxr3, JLSEC-2025-146, UBUNTU-CVE-2023-6601, openSUSE-SU-2026:10027-1, openSUSE-SU-2026:10028-1

## What is CVE-2023-6601?

CVE-2023-6601 is a medium-severity code injection vulnerability in Ffmpeg Ffmpeg, published on 6 Jan 2025. 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

A flaw was found in FFmpeg's HLS demuxer. This vulnerability allows bypassing unsafe file extension checks and triggering arbitrary demuxers via base64-encoded data URIs appended with specific file extensions.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-99 (Improper Control of Resource Identifiers)

## Which versions are affected by CVE-2023-6601?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ffmpeg-4` | openSUSE:Tumbleweed | All versions | 4.4.6-10.1 |
| `ffmpeg-7` | openSUSE:Tumbleweed | All versions | 7.1.3-1.1 |

Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2023-6601?

Apply the vendor's patch.

## Is CVE-2023-6601 being exploited?

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

What it is: CVE-2023-6601 is a medium-severity code injection vulnerability in Ffmpeg Ffmpeg, published on 6 Jan 2025. 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-2023-6601 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-2023-6601/ (Markdown: https://insights.sbomify.com/CVE-2023-6601/index.md)
```

## Sources

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

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