Skip to main content

MyTube EUVDEUVD-2026-114369

| CVE-2026-62302 HIGH
Missing Authentication for Critical Function (CWE-306)
2026-10-30 GitHub_M
8.7
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

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

  1. Access
    Reach MyTube instance with loginEnabled=true
  2. Exploit
    Request media path directly without auth
  3. Impact
    Download private/hidden video, subtitle, or image files

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial 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 instance to be deployed in multi-user mode with loginEnabled=true (admin/visitor passwords configured); in that mode the static routes (registerStaticRoutes) and cloud proxy routes (registerCloudRoutes) are registered in server.ts before registerApiRoutes, so the authMiddleware/roleBasedAuthMiddleware stack never applies to /videos/*, /images/*, /images-small/*, /avatars/*, /subtitles/*, /api/cloud/thumbnail-cache/*, /cloud/videos/:filename, and /cloud/images/:filename. No credentials, cookie, token, or user interaction are needed to fetch these. LIMITING FACTORS: the default loginEnabled=false single-user deployment is NOT affected (no auth boundary exists to bypass); cloud routes return 404 when cloud storage is unconfigured (a route-handler response, not an auth rejection); and downloading specific hidden media additionally depends on knowing or leaking the file path (the separate hidden-video path leak).

Impact

Severity signals are moderately strong but conditional. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remotely reachable, low-complexity, unauthenticated flaw, and the confidentiality-only impact (VC:H, VI:N, VA:N, no scope change to other systems) matches CWE-306 (Missing Authentication): the real-world effect is unauthorized disclosure of media, not code execution or tampering. The vuln.today decision label is 'this_week' (not act_now/emergency). No CISA KEV entry is present in the input and no EPSS score was supplied, so there is no evidence of active or widespread exploitation - the status is 'no public exploit identified as actively exploited'; however, the GHSA advisory itself contains a working curl-based PoC, so the barrier to abuse is effectively zero for anyone who reads it. The dominant caveat is configuration dependence: the flaw ONLY matters when loginEnabled=true (multi-user mode with admin/visitor passwords). The default deployment (loginEnabled=false, single-user) has no authentication boundary to bypass and is therefore not affected. So although the raw vector reads as a textbook 8.7 unauthenticated network issue, real priority is bounded by (a) how many instances run in multi-user mode and (b) the small deployment footprint of this self-hosted hobby project. No SSVC automatable/technical-impact decision data was provided to further weigh this. Net: a genuine, trivially exploitable authentication-bypass for multi-user instances, but scoped to confidentiality of media and gated by a non-default configuration.

Exploit ScenarioDerived

An attacker who can reach a MyTube instance running in multi-user mode (loginEnabled=true) requests media paths such as /videos/private.mp4, /subtitles/private.vtt, /images/* or /cloud/videos/:filename directly, with no cookie or token, and receives the content despite the frontend login wall. A working PoC (curl commands) is published in the GHSA advisory; combined with hidden-video path leaks, the attacker can enumerate and download private or hidden media without ever authenticating.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 30, 2026

MyTube deployments running in multi-user mode (loginEnabled=true) expose all locally stored and cloud-proxied media - videos, thumbnails, small thumbnails, avatars, subtitles and cloud signed URLs - to unauthenticated clients because the static and cloud route handlers are mounted before the authentication middleware. An attacker with network reach to the instance can fetch /videos/*, /images/*, /subtitles/*, /avatars/*, /api/cloud/thumbnail-cache/* and /cloud/videos|images/:filename without any session cookie, token or user interaction, and can combine this with the separate hidden-video path leak to download media the operator intended to hide. The default single-user configuration (loginEnabled=false) has no authentication boundary and is not affected; the flaw is fixed in version 1.10.3, a public PoC reference (curl-based request examples) is documented in the advisory, and there is no indication of confirmed active exploitation (no CISA KEV listing).

RemediationAI

Upgrade to MyTube v1.10.3, which is the vendor-released patch that moves static media serving behind a session-checking controller and adds the requireAuthenticatedMediaAccess middleware for static, cloud and media paths (fix commit https://github.com/franklioxygen/MyTube/commit/7cc7c6a7d297ccbd8bd2c76755129381b96f8456, release tree https://github.com/franklioxygen/MyTube/tree/v1.10.3, advisory https://github.com/franklioxygen/MyTube/security/advisories/GHSA-rwwf-29mq-5j43); the vendor states that updating to 1.10.3 is the complete fix. Because the vulnerable routes are reachable without credentials, evidence that an instance was probed cannot be obtained from authentication logs; audit access logs for unauthenticated 200 responses on /videos/, /images/, /images-small/, /avatars/, /subtitles/, /api/cloud/thumbnail-cache/ and /cloud/ paths. Operators who cannot upgrade immediately can compensate at the network edge by placing the instance behind a reverse proxy that enforces authentication on exactly those path prefixes, with the trade-off that RSS media feeds (rss token query/cookie), API-key-driven clients and cloud redirect flows will break unless the proxy is made aware of those tokens, and that the frontend's own login wall provides no protection for direct media requests. Instances deliberately run in single-user mode with loginEnabled=false are not exposed by this flaw, but any deployment that enables login must be treated as affected until it reaches 1.10.3.

Affected VersionsENISA

MyTube < 1.10.3

Affected Packages

euvd mytube fix: 1.10.3

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

MyTube is a Node/Express application that serves a React frontend plus media assets. In server.ts, registerStaticRoutes(app, frontendDist) and registerCloudRoutes(app) are invoked before registerApiRoutes(app, ...), and the authMiddleware / roleBasedAuthMiddleware stack is only mounted inside registerApiRoutes. Express evaluates middleware in registration order, so every handler attached earlier is served without ever entering the auth stack - the classic CWE-306 "missing authentication for critical function" pattern, where the protection exists in the codebase but is applied to the wrong subset of routes. The bypassed surface includes local video files under /videos/*, thumbnails under /images/* and /images-small/*, author avatars under /avatars/*, subtitle files (VTT/SRT) under /subtitles/*, the cloud thumbnail cache under /api/cloud/thumbnail-cache/*, and cloud storage proxy endpoints /cloud/videos/:filename and /cloud/images/:filename that mint signed URLs or 302 redirects. A subtle diagnostic detail: unauthenticated requests to protected API routes such as /api/videos are correctly rejected with 401, while cloud routes answer 404 when cloud storage is not configured - that 404 originates in the route handler (cloudRoutes.ts), not in an authentication decision, so the absence of a 401 on those paths is not evidence of protection. The upstream fix (commit 7cc7c6a7) introduces a dedicated mediaAuthMiddleware (requireAuthenticatedMediaAccess) that permits access only when login is not required, when a valid session user is present, when the request was API-key authenticated, or when a valid active RSS token is supplied via query parameter or the mytube_rss_token cookie, and additionally scopes video lookups so a visitor role cannot resolve hidden videos.

Know when Mytube gets its next vulnerability

  • 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 (GitHub_M) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Remotely reachable static routes bypass auth entirely so AV:N/AC:L/PR:N/UI:N; impact is unauthorized read of all media (C:H) with no integrity or availability effect and no scope change.

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Lifecycle Timeline

2
Patch available
Oct 30, 2026 - 21:18 EUVD
CVE Published
Oct 30, 2026 - 19:29 cve.org
HIGH 8.7

DescriptionCVE.org

MyTube is a self-hosted downloader and player for several video websites. Prior to version 1.10.3, server.ts calls registerStaticRoutes and registerCloudRoutes before registerApiRoutes, where authMiddleware and roleBasedAuthMiddleware are mounted. Because Express processes middleware in registration order, staticRoutes.ts and cloudRoutes.ts remain outside the authentication stack even when loginEnabled=true. Unauthenticated clients can access local videos through /videos/*, thumbnails through /images/* and /images-small/*, avatars through /avatars/*, subtitles through /subtitles/*, cloud thumbnail caches through /api/cloud/thumbnail-cache/*, and cloud signed URLs or redirects through /cloud/videos/:filename and /cloud/images/:filename. The frontend login wall does not protect direct media requests. Cloud routes return 404 when cloud storage is unconfigured, but that is not an authentication rejection; protected API routes correctly return 401. Combined with hidden-video path leaks, the flaw permits unauthenticated downloads of hidden media. Default loginEnabled=false single-user deployments have no authentication boundary to bypass. This issue is fixed in version 1.10.3.

Technical POC Analysis

CWE-306, Missing Authentication for Critical Function, implemented as an Express middleware-ordering defect in MyTube's own server bootstrap.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

CVE-2026-62302 is a high-severity vulnerability in MyTube deployments configured for multi-user mode (loginEnabled=true), where improper route ordering allows unauthenticated access to all locally stored and cloud-proxied media, including videos, thumbnails, avatars, and cloud signed URLs. This means any individual with network access to the instance can bypass authentication and retrieve potentially sensitive media, undermining the intended access controls. Leadership should prioritize remediation because this exposure can lead to unauthorized disclosure of confidential or private content, damage to organizational reputation, and potential regulatory non-compliance, especially if the media contains personal or proprietary information.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Low
niche self-hosted single-developer GitHub project, small deployment footprint
Data Quality
5 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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