CVE-2026-23837
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMyTube 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().
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMyTube versions 1.7.65 and earlier contain an authentication bypass in the roleBasedAuthMiddleware where requests without an authentication cookie (resulting in undefined req.user) incorrectly proceed to protected endpoints instead of being blocked. This allows unauthenticated attackers to access /api/settings, modify passwords, and reach other protected routes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.7.66CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mytube versionCheck the package.json, version file, or run a version command (e.g., npm list mytube, mytube --version) if available in the deploymentAffected if The installed version is 1.7.65 or lower (anything below 1.7.66)
-
Verify roleBasedAuthMiddleware is in useSearch the codebase for 'roleBasedAuthMiddleware' in source files, typically in middleware or route configuration filesAffected if The middleware exists and handles authentication for API routes
-
Test unauthenticated access to protected endpointsSend an HTTP request to /api/settings (or another protected /api/ endpoint) without any authentication cookie or token using curl or a browserAffected if The request returns successful data (200 OK) instead of a 401/403 error, indicating the bypass is active
-
Check for undefined req.user handlingInspect the roleBasedAuthMiddleware code - look for conditional logic that handles cases where req.user may be undefined or missingAffected if The middleware lacks a check that returns 401 when req.user is undefined (the code proceeds to next() without blocking)
-
Verify API endpoint exposureConfirm that /api/ endpoints are internet-facing or accessible from untrusted networksAffected if The API endpoints are publicly accessible without network-level restrictions
You are affected if running Mytube version 1.7.65 or earlier AND the roleBasedAuthMiddleware is active AND unprotected /api/ endpoints return data to unauthenticated requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.7.66
Upgrade to v1.7.66 or later immediately. If immediate upgrade is not possible, restrict access to /api/ endpoints via firewall or reverse proxy to trusted IPs, or manually patch roleBasedAuthMiddleware to return 401 when req.user is undefined.
v1.7.66
- Back up your current MyTube installation and configuration before proceeding
- Stop the MyTube service to prevent any active sessions during the upgrade
- Upgrade MyTube to version 1.7.66 or later by following your deployment method (e.g., package manager, docker pull, or source update)
- Verify the upgrade was successful by checking the installed version
- Restart the MyTube service
- Confirm that the authentication middleware is now properly blocking unauthenticated requests by testing access to /api/settings without credentials - it should return 401 Unauthorized
- If using Docker, pull the latest image or specify version 1.7.66: `docker pull franklioxygen/mytube:1.7.66` or update your docker-compose.yml
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23837 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23837 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data