Skip to main content

MeTube EUVDEUVD-2026-104059

| CVE-2026-112076 LOW
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-19 cna@vuldb.com GHSA-g899-4284-8gqj
2.9
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit crafted playlist/channel URL to MeTube
  2. Exploit
    Feed-metadata handler reads attacker-controlled thumbnail URL
  3. Execution
    Server fetches internal/cloud-metadata endpoint
  4. Impact
    Internal response written to download directory and served via /download

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to get a MeTube instance to process a feed (playlist or channel) whose thumbnail URL the attacker controls, and the instance must have metadata/thumbnail writing enabled (the regression test sets YTDL_OPTIONS writeinfojson=True and writethumbnail=True), triggering the __write_feed_metadata_sync path that fetches and persists the thumbnail. Limiting factors: the attack is explicitly rated highly complex and difficult to exploit (CVSS AC:H); impact is confined to retrieving an internal HTTP response written to the download directory (no RCE); and realistic exploitation depends on the target MeTube being reachable by the attacker and on network-adjacent internal services actually existing behind it. MeTube commonly runs without authentication, consistent with the CVSS PR:N.

Impact

This is a genuinely low-priority issue despite being network-reachable and unauthenticated. The CVSS 4.0 base vector (AV:N/AC:H/PR:N/UI:N/VC:L/VI:L/VA:L) scores only 2.9, and the high attack complexity (AC:H) is corroborated by the description's explicit statements that 'Attacks of this nature are highly complex' and 'the exploitability is difficult' - the signals agree rather than conflict. The E:P temporal metric and the description confirm publicly available exploit code exists, but this is a proof-of-concept, NOT active exploitation: the CVE is not listed in CISA KEV and no EPSS score was provided in the input, so real-world exploitation likelihood cannot be quantified. The technical impact is limited (all three impact metrics are Low) because the SSRF only allows fetching an internal response that is written to the download directory and served via /download - there is no code execution or full data exfiltration. The combination of high complexity, low impact, PoC-only status, and no KEV listing means this should be patched during normal maintenance rather than treated as an emergency. The source-code evidence (added SSRF-guard tests and the socket_guard_scope mitigation) confirms the vulnerability class is real and was deliberately fixed.

Exploit ScenarioDerived

An attacker crafts a malicious playlist or channel feed whose thumbnail URL points at an internal service (e.g., a cloud metadata endpoint or an internal admin host) and induces a MeTube instance to process it; the server-side feed-metadata handler fetches that thumbnail and writes the internal response into the download directory, where it can then be retrieved via /download. A public proof-of-concept exists, but the attack is difficult and highly complex (CVSS AC:H), and the added regression tests show redirect-based pivots were also considered.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

Server-side request forgery in alexta69 MeTube (up to 2026.09.28) allows a remote, unauthenticated attacker who can influence a playlist or channel feed to make the instance fetch an arbitrary thumbnail URL - including redirects - from its own network position, writing the internal HTTP response into the download directory that /download serves back. The flaw sits in DownloadQueue.__write_feed_metadata_sync (app/ytdl.py) and is only reachable when metadata/thumbnail writing is enabled (writeinfojson/writethumbnail); exploitation is rated highly complex (AC:H, CVSS 4.0 base 2.9) and impact is limited to internal-response disclosure with no code execution. Publicly disclosed proof-of-concept exploitation details exist (CVSS E:P), and the issue is fixed in release 2026.09.29; it is not listed in CISA KEV, so there is no confirmation of active in-the-wild exploitation.

RemediationAI

Upgrade to MeTube 2026.09.29 or later - the vendor-released patch (release 2026.09.29, commit a3896604540223ecbb8258b41b1d745d62647d16, advisory GHSA-hq22-f7w6-p8cr) adds the thread-scoped socket guard around the feed-metadata fetch; re-pull the container image rather than reusing a cached 2026.09.28 layer. If an immediate upgrade is not possible, remove or set to false the writeinfojson and writethumbnail entries in YTDL_OPTIONS so the vulnerable thumbnail fetch is never performed - the trade-off is loss of cached thumbnails and .info.json metadata for playlist/channel downloads. As a second compensating control, apply egress filtering at the container/network layer to block MeTube's outbound traffic to RFC1918 ranges, loopback, link-local 169.254.169.254 (cloud metadata) and other internal service ports, accepting that this may also block legitimate media sources hosted internally. Because MeTube is commonly deployed without authentication (consistent with the PR:N vector), also place the instance behind an authenticating reverse proxy or restrict it to trusted networks to reduce who can submit attacker-controlled feed URLs at all.

Affected VersionsENISA

MeTube 2026.09.24
MeTube 2026.09.22
MeTube 2026.09.8
MeTube 2026.09.14
MeTube 2026.09.17
MeTube 2026.09.1
MeTube 2026.09.27
MeTube 2026.09.4
MeTube 2026.09.6
MeTube 2026.09.11
MeTube 2026.09.0
MeTube 2026.09.23
MeTube 2026.09.10
MeTube 2026.09.21
MeTube 2026.09.2
MeTube 2026.09.9
MeTube 2026.09.18
MeTube 2026.09.15
MeTube 2026.09.20
MeTube 2026.09.16
MeTube 2026.09.25
MeTube 2026.09.12
MeTube 2026.09.28
MeTube 2026.09.13
MeTube 2026.09.19
MeTube 2026.09.7
MeTube 2026.09.3
MeTube 2026.09.5
MeTube 2026.09.26

Affected Packages

euvd metube no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MeTube is a Python web front end for yt-dlp. During playlist/channel processing the download queue calls __write_feed_metadata_sync, which reads the feed's 'thumbnail' URL, fetches it with urllib, and persists the bytes next to the generated .info.json in DOWNLOAD_DIR so that the /download endpoint can serve them. Because this pass executes in the main web process, the project's existing SSRF defense - url_guard, which monkey-patches socket.getaddrinfo to reject private, loopback and link-local resolutions such as 169.254.169.254 - did not cover it. The upstream fix introduces socket_guard_scope, a thread-local variant of the guard that installs a scoped getaddrinfo for the guarded thread only (leaving _allowed_endpoints process-wide state untouched), while still permitting explicitly configured proxy and service endpoints. It also updates the redirect handling path so a 302 from the attacker-supplied thumbnail URL cannot pivot to an internal host. This is class CWE-918: the application accepts a user-controlled URL and performs a server-side request without validating that the destination is not an internal resource. The accompanying regression tests (test_feed_thumbnail_cannot_reach_internal_hosts with redirect=False/True, and SocketGuardScopeTests) confirm the guard applies only within the scope, lifts cleanly, and that a refused thumbnail is a non-fatal warning - the rest of the metadata still lands.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 2.9 MEDIUM
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 5.6 MEDIUM

Network-reachable thumbnail fetch with no auth (MeTube default, PR:N) but difficult to trigger (AC:H); impact limited to retrieving one internal response written to disk, so C/I/A all Low.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (vuldb).

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A security vulnerability has been detected in alexta69 MeTube up to 2026.09.28. This vulnerability affects the function DownloadQueue.__write_feed_metadata_sync of the file app/ytdl.py of the component Feed-metadata Thumbnail Fetch Handler. Such manipulation leads to server-side request forgery. The attack may be launched remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 2026.09.29 is able to resolve this issue. The name of the patch is a3896604540223ecbb8258b41b1d745d62647d16. It is suggested to upgrade the affected component.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Low
niche self-hosted media downloader, homelab use, no enterprise footprint
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

14
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +14
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy