# CVE-2026-50019: yt-dlp: File Downloader cookie leak with curl

> Attackers can leak user cookies to unintended hosts when using curl as an external downloader in yt-dlp during redirects or fragment downloads.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/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:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-50019, GHSA-f7j3-774f-rfhj, PYSEC-2026-3431, UBUNTU-CVE-2026-50019

## What is CVE-2026-50019?

CVE-2026-50019 is a medium-severity vulnerability in yt-dlp, published on 23 Jun 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

yt-dlp is a command-line audio/video downloader. From 2023.09.24 until 2026.06.09, if curl is used as an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest's. At the file download stage, the cookies are passed by yt-dlp to the file downloader via --cookie. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, curl will send cookies with requests to domains or paths for which the cookies are not scoped. This vulnerability is fixed in 2026.06.09.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including yt-dlp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yt-dlp` | PyPI | From 2023.9.24 | 2026.6.9 |
| `yt-dlp` | PyPI | From 2023.9.24 | 2026.6.9 |
| `yt-dlp` | PyPI | From 2023.9.24 | 2026.6.9 |

Products: Yt-Dlp Project Yt-Dlp.

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

Upgrade yt-dlp to 2026.6.9 or later.

## Is CVE-2026-50019 being exploited?

There is no known exploitation of CVE-2026-50019 in the wild and no public exploit code.

## Other vulnerabilities in yt-dlp

- [CVE-2026-26331](https://insights.sbomify.com/CVE-2026-26331/): yt-dlp: Arbitrary Command Injection when using the `--netrc-cmd` option (high 8.8)
- [CVE-2024-22423](https://insights.sbomify.com/CVE-2024-22423/): yt-dlp `--exec` command injection when using `%q` in yt-dlp on Windows (high 8.4)
- [CVE-2023-40581](https://insights.sbomify.com/CVE-2023-40581/): yt-dlp command injection when using `%q` in `--exec` on Windows (high 8.4)
- [CVE-2026-50023](https://insights.sbomify.com/CVE-2026-50023/): yt-dlp: Dangerous file type creation via insufficient filename sanitization (Bypass of CVE-2024-38519) (high 8.3)
- [CVE-2026-50574](https://insights.sbomify.com/CVE-2026-50574/): yt-dlp: Arbitrary code execution via manifest downloads with aria2c (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50019 and fix it if it is affected.

What it is: CVE-2026-50019 is a medium-severity vulnerability in yt-dlp, published on 23 Jun 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-50019 in the wild and no public exploit code.

Affected packages and fixed versions:
- yt-dlp (PyPI): affected from 2023.9.24; fixed in 2026.6.9
- yt-dlp (PyPI): affected from 2023.9.24; fixed in 2026.6.9
- yt-dlp (PyPI): affected from 2023.9.24; fixed in 2026.6.9

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

## Sources

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

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