LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23837: MyTube has an Authorization Bypass vulnerability

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().

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-23837 lets unauthenticated attackers bypass MyTube’s login protection on affected self-hosted instances. If login is enabled, protected API routes may be reachable without a valid session, including settings and password changes. This is business-critical where MyTube is internet-accessible because it can lead to full application compromise.

Executive priority

Treat this as urgent for any exposed MyTube instance. The vulnerability can bypass login and alter sensitive settings or passwords. Prioritize patching or network restriction before routine maintenance windows, especially for internet-facing deployments.

Technical view

MyTube versions before 1.7.66 contain an authorization bypass in roleBasedAuthMiddleware. When req.user is undefined, the middleware can incorrectly continue to downstream handlers instead of rejecting the request. The CVE cites access to /api/settings, administrative and visitor password changes, and other routes relying on this middleware. CVSS is 9.8, CWE-863.

Likely exposure

Self-hosted MyTube deployments running versions below 1.7.66 with loginEnabled: true are impacted. Internet-facing instances are the highest concern. Instances with /api/ routes reachable from untrusted networks have elevated risk.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The weakness is network-reachable, requires no authentication, no user interaction, and has low attack complexity according to the CVSS vector.

Researcher notes

The source bundle names affected versions as below 1.7.66 and says the fix blocks unauthenticated requests when req.user is undefined. One description line says maintainers recommend upgrading to at least v1.7.64, which conflicts with the stated patched version 1.7.66. Validate against the GitHub advisory before closing remediation.

Mitigation direction

  • Upgrade MyTube to version 1.7.66 or later where the issue is patched.
  • If unable to upgrade, restrict /api/ access to trusted IP addresses only.
  • Use a firewall or reverse proxy to limit network exposure.
  • If manually patching, follow vendor guidance for roleBasedAuthMiddleware behavior.
  • Review vendor advisory for the latest recommended fixed version.

Validation and detection

  • Identify all MyTube instances and their running versions.
  • Confirm whether loginEnabled is set to true.
  • Verify internet and internal exposure of /api/ routes.
  • Confirm upgraded instances run version 1.7.66 or later.
  • Review logs for unauthenticated access to /api/settings or protected routes.
  • If manually patched, verify unauthenticated requests are rejected.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23837 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-23837Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
franklioxygenMyTube< 1.7.66Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.