dbcve.org
MytubeApplication · Franklioxygen

CVE-2026-33890

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 1.8.71 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
MyTube is a self-hosted downloader and player for several video websites Prior to version 1.8.71, an unauthenticated attacker can register an arbitrary passkey and subsequently authenticate with it to obtain a full admin session. The application exposes passkey registration endpoints without requiring prior authentication. Any successfully authenticated passkey is automatically granted an administrator token, allowing full administrative access to the application. This enables a complete compromise of the application without requiring any existing credentials. Version 1.8.71 fixes the issue.

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 confidence

MyTube versions prior to 1.8.71 expose passkey registration endpoints without requiring prior authentication. An unauthenticated attacker can register an arbitrary passkey and then authenticate with it. The application automatically grants administrator privileges to any successfully authenticated passkey, providing full admin session access and complete application compromise without existing credentials.

MitigationUpgrade MyTube to version 1.8.71 or later to remediate the unauthenticated passkey registration vulnerability. If immediate upgrade is not possible, disable or restrict passkey registration endpoints at the network level until the patch can be applied.

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
MytubeApplication
Affected:< 1.8.71

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed MyTube version
    Locate the application version through its UI settings, about page, or by inspecting the application's binary/metadata. Common locations include the Help menu, Settings > About, or the executable file properties.
    Affected if The installed version is lower than 1.8.71
  2. Verify passkey functionality status
    Check whether the passkey registration feature is enabled in the application settings or configuration. Look for passkey, biometric, or authentication-related settings within the application admin panel or configuration files.
    Affected if Passkey registration is currently enabled and accessible without authentication barriers
  3. Examine passkey privilege assignment configuration
    Inspect the application's authentication or security configuration to determine whether registered passkeys are automatically granted administrator-level privileges. Check role-based access control settings related to passkey authentication.
    Affected if Passkey-based authentication is configured to automatically assign full administrator privileges to any successfully registered passkey
  4. Test unauthenticated passkey registration
    If you have administrative access, attempt to register a new passkey through the application's passkey registration interface without first authenticating with existing credentials.
    Affected if Passkey registration succeeds without requiring prior authentication

Your environment is affected if MyTube version is below 1.8.71 AND the passkey feature is enabled, particularly if passkey registration does not require authentication or automatically grants admin privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.8.71 or later
Fixed in 1.8.71
Vendor patch github.com →
Interim mitigation

Upgrade MyTube to version 1.8.71 or later to remediate the unauthenticated passkey registration vulnerability. If immediate upgrade is not possible, disable or restrict passkey registration endpoints at the network level until the patch can be applied.

Recommended fix High confidence

1.8.71

  1. Upgrade Mytube to version 1.8.71 or later to obtain the security patch
  2. After upgrading, review existing admin sessions and passkey registrations for any unauthorized entries
  3. Verify that passkey registration now requires authentication before allowing registration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mytube Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33890 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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