← Back
CVE-2026-26331
OS Command Injection in yt-dlp (CVE-2026-26331)
Summary
OS command injection in yt-dlp (CVE-2026-26331). Successful exploitation can lead to full system takeover. Exploitable via ``netrc_cmd``. Mitigation: upgrade to `2026.02.21` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-26331** has been found in yt-dlp.
Attackers can target a specific entry point like ``netrc_cmd`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade yt-dlp to **2026.02.21** or later.
If unsure, ask your IT team or search "yt-dlp CVE-2026-26331" on the vendor's site.
CVE-2026-26331 (yt-dlp) — CWE-78 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `netrc_cmd` / `GetCourseRuIE` / `TeachableIE` / `TeachableCourseIE`
Patched: `2026.02.21` — 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
**OS command injection** (CWE-78) exists in yt-dlp. Attackers reach the vulnerable code path via ``netrc_cmd`` without authentication.
📍 Affected scope
yt-dlp — . Attack surface: `netrc_cmd` / `GetCourseRuIE` / `TeachableIE` / `TeachableCourseIE`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2026.02.21**.
🛡️ 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.02.21ステージング環境で 2026.02.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
yt-dlp
[{"type":"ECOSYSTEM","events":[{"introduced":"2023.06.21"},{"fixed":"2026.02.21"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-26331
- advisory https://github.com/advisories/GHSA-g3gw-q23r-pgqm
- package https://github.com/yt-dlp/yt-dlp
- package https://pypi.org/project/yt-dlp
- web https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-g3gw-q23r-pgqm
- web https://github.com/yt-dlp/yt-dlp/commit/1fbbe29b99dc61375bf6d786f824d9fcf6ea9c1a
- web https://github.com/yt-dlp/yt-dlp/releases/tag/2026.02.21