← Back
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.
AI summary snake-internal / snake-material-v2
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
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'yt-dlp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `yt-dlp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade yt-dlp to 2026.6.9ステージング環境で 2026.6.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
yt-dlp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.9"}]}]
References
- patch [email protected]
- web https://github.com/yt-dlp/yt-dlp/commit/2726572520238356bcf64aba2040228648b44c82
- web https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/tag/2026.06.09.230517
- web https://github.com/yt-dlp/yt-dlp/releases/tag/2026.06.09
- web https://github.com/advisories/GHSA-f7j3-774f-rfhj