CVE-2026-62301

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-114368 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

November 6, 2026

Advisory Details (5)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit f9ae048cc37c (franklioxygen/MyTube)

Fix landed in franklioxygen/MyTube commit f9ae048cc37c — awaiting tagged release

https://github.com/franklioxygen/MyTube/commit/f9ae048cc37c98a3576115d8841f8e96bade5c76
GitHub commit

commit 905cecc010f3 (franklioxygen/MyTube)

Fix landed in franklioxygen/MyTube commit 905cecc010f3 — awaiting tagged release

https://github.com/franklioxygen/MyTube/commit/905cecc010f320ab4e575eb3054179e9616a0b39
GitHub commit

commit 7cc7c6a7d297 (franklioxygen/MyTube)

Fix landed in franklioxygen/MyTube commit 7cc7c6a7d297 — awaiting tagged release

https://github.com/franklioxygen/MyTube/commit/7cc7c6a7d297ccbd8bd2c76755129381b96f8456
GitHub commit

commit 456d09892b59 (franklioxygen/MyTube)

Fix landed in franklioxygen/MyTube commit 456d09892b59 — awaiting tagged release

https://github.com/franklioxygen/MyTube/commit/456d09892b599e78538ef1a795f49b91256c3ca6
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Visitor Can Access Hidden Video Metadata and Content · Advisory · franklioxygen/MyTube · GitHub

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-11 03:55 UTCEchelonGraph re-scored
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-11-06 18:29 UTCEchelonGraph re-scored
  9. 2026-11-06 18:27 UTCEchelonGraph re-scored
  10. 2026-11-06 17:43 UTCEchelonGraph re-scored
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-11-03 20:19 UTCEchelonGraph re-scored
  15. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-11-02 19:46 UTCEchelonGraph re-scored
  17. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-30 21:02 UTCENISA EUVD ID recordedEUVD-2026-114368 · Source: ENISA EUVD
  21. 2026-10-30 20:26 UTCEchelonGraph re-scored
  22. 2026-10-30 19:30 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  23. 2026-10-30 19:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62301?
CVE-2026-62301 is a high-severity vulnerability; its CVE record was published on October 30, 2026. 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…
When was the CVE record for CVE-2026-62301 published?
The CVE record for CVE-2026-62301 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-62301 actively exploited?
CVE-2026-62301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62301?
CVE-2026-62301 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62301?
The CVE record for CVE-2026-62301 names the fix: "This issue is fixed in version 1.10.3."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62301

Explore →

Is Your Infrastructure Affected by CVE-2026-62301?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs