CVE-2026-23837: franklioxygen MyTube · Incorrect Authorization
Affects franklioxygen MyTubeSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.7.66 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.66
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade MyTube and franklioxygen/MyTube to 1.7.66.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| franklioxygenMyTube | Affected
| Fixed in
|
GitHubfranklioxygen/MyTubepkg:github/franklioxygen/MyTubeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade of all MyTube instances to version 1.7.66 or later is the most effective mitigation. 2. Until upgrade is possible, restrict access to /api/ endpoints using network-level controls such as firewalls or reverse proxies (e.g., Nginx) to allow only trusted IP addresses. 3. For organizations with development resources, manually patch the roleBasedAuthMiddleware by modifying the logic to return a 401 Unauthorized error when req.user is undefined instead of calling next(). 4. 5. Monitor logs for unusual access patterns to /api/settings or other protected routes that could indicate exploitation attempts. 6. Implement network segmentation to isolate MyTube servers from critical infrastructure. 7. Educate administrators on the importance of timely patching and secure configuration management. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized API requests targeting MyTube endpoints.
Description
MyTube is a self-hosted downloader and player for several video websites. A vulnerability present in version 1.7.65 and poetntially earlier versions allows unauthenticated users to bypass the mandatory authentication check in the roleBasedAuthMiddleware. By simply not providing an authentication cookie (making req.user undefined), a request is incorrectly passed through to downstream handlers. All users running MyTube with loginEnabled: true are impacted. This flaw allows an attacker to access and modify application settings via /api/settings, change administrative and visitor passwords, and access other protected routes that rely on this specific middleware. The problem is patched in v1.7.66. MyTube maintainers recommend all users upgrade to at least version v1.7.64 immediately to secure their instances. The fix ensures that the middleware explicitly blocks requests if a user is not authenticated, rather than defaulting to next(). Those who cannot upgrade immediately can mitigate risk by restricting network access by usi a firewall or reverse proxy (like Nginx) to restrict access to the /api/ endpoints to trusted IP addresses only or, if they are comfortable editing the source code, manually patch by locating roleBasedAuthMiddleware and ensuring that the logic defaults to an error (401 Unauthorized) when req.user is undefined, instead of calling next().