cve.bz

CVE-2026-50019 yt-dlp project yt-dlp

7.4 highEPSS 0.3%Fix available

High (7.4) in yt-dlp project yt-dlp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in yt-dlp 2026.6.9.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-50019 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50019?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50019?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50019 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
yt-dlp_project:yt-dlpfrom 2023.09.24 before 2026.06.09

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f7j3-774f-rfhjPyPIyt-dlp>=2023.9.24 <2026.6.92026.6.9
PYSEC-2026-3431PyPIyt-dlp>=2023.9.24 <2026.6.92026.6.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13yt-dlpno fix listedDEBIAN-CVE-2026-50019
Debian14yt-dlp2026.06.09-1DEBIAN-CVE-2026-50019
Ubuntu22.04:LTS, 24.04:LTS, 25.10 and 2 moreyt-dlpno fix listedUBUNTU-CVE-2026-50019
openSUSELeap 16.0yt-dlp2026.06.09-bp160.1.1openSUSE-SU-2026:21163-1
openSUSETumbleweedyt-dlp2026.06.09-1.1openSUSE-SU-2026:11019-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON