CVE-2026-50019: yt-dlp: File Downloader cookie leak with curl
Summary If curl is used 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.
This is the equivalent to GHSA-v8mc-9377-rwjj for the curl downloader. The vulnerable behavior is present in yt-dlp released since 2023.09.24.
Details 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.
An example of a potential attack scenario exploiting this vulnerability: 1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an unvalidated redirect to a target URL. 2. yt-dlp extracts this URL and calculates the cookies which are then passed to curl. 3. the download URL redirects to a server controlled by the attacker, to which curl forwards the user's sensitive cookie information.
Patches yt-dlp version 2026.06.09 fixes this issue by doing the following:
- Pass the cookies through stdin via --cookie - if curl is version 7.59 or higher. - Pass the cookies via --cookie /dev/fd/0 if the system supports this device file. - In all other cases create a temporary file, save the cookies and then pass via --cookie <file>.
Workarounds It is recommended to upgrade yt-dlp to version 2026.06.09 as soon as possible.
For users who are not able to upgrade:
- Do not use --downloader curl.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/yt-dlpto a version that resolves this vulnerability.Fixed in 2026.6.9 - Upgrade
Upgrade
yt-dlpto a version that resolves this vulnerability.Fixed in 2026.06.09 - Configuration
Do not use `--downloader curl`; instead use a method that does not pass cookies to curl in a way that triggers cookie leakage during redirects.
curl (used as external downloader for yt-dlp) --downloader = curl - Configuration
For all other cases, create a temporary file, save cookies to it, and pass them via `--cookie <file>`.
curl (used as external downloader for yt-dlp) --cookie = <file> - Configuration
If the system uses curl version 7.59 or higher, pass cookies through stdin via `--cookie -`.
curl (used as external downloader for yt-dlp) --cookie = - - Configuration
If the system supports this device file, pass cookies via `--cookie /dev/fd/0`.
curl (used as external downloader for yt-dlp) --cookie = /dev/fd/0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-50019?
The severity of CVE-2026-50019 is classified as medium with a score of 6.1.
What does CVE-2026-50019 affect?
CVE-2026-50019 affects the pip and yt-dlp software when curl is used as an external downloader.
How does CVE-2026-50019 exploit the system?
CVE-2026-50019 can lead to cookie leaks to unintended hosts due to HTTP redirects or differing download fragment hosts.
What is the risk associated with CVE-2026-50019?
CVE-2026-50019 has a risk rating of 35, indicating potential information leakage.
How can I mitigate the impact of CVE-2026-50019?
To mitigate CVE-2026-50019, ensure that you are using the latest version of yt-dlp that addresses this vulnerability.