Categories
CVE-2026-50019 medium CVSS 6.1

Information Disclosure in yt-dlp (CVE-2026-50019)

Summary

Vulnerability in yt-dlp (CVE-2026-50019). Confidential information can be exposed externally. Exploitable via curl. Mitigation: upgrade to 2026.6.9 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-50019 has been found in yt-dlp.
Attackers can target a specific entry point like curl over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: upgrade yt-dlp to 2026.6.9 or later.
If unsure, ask your IT team or search "yt-dlp CVE-2026-50019" on the vendor's site.

CVE-2026-50019 (yt-dlp) — CWE-200 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: curl
Patched: 2026.6.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in yt-dlp. Attackers reach the vulnerable code path via curl without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of yt-dlp. Attack surface: curl.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.6.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'yt-dlp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'yt-dlp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で yt-dlp を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade yt-dlp to 2026.6.9

    ステージング環境で 2026.6.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip yt-dlp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.9"}]}]
PyPI yt-dlp
[{"type":"ECOSYSTEM","events":[{"introduced":"2023.9.24"},{"fixed":"2026.6.9"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details