Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.3
CVE-2026-33935: MyTube allows attackers to lock out user accounts
CVE-2026-33935 · published 7 months ago
Summary
The self‑hosted MyTube video downloader (versions before 1.8.72) stores login attempts in a single file that is shared by all login pages. An unauthenticated user can repeatedly submit wrong passwords to any login page, causing the shared counter to trigger a cooldown that eventually blocks all legitimate users for up to 24 hours. Update MyTube to version 1.8.72 or later, or apply a patch that separates the login‑attempt tracking for each endpoint.
What to do
- Update franklioxygen mytube to version 1.8.72 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| franklioxygen | mytube |
< 1.8.72 cpe:2.3:a:franklioxygen:mytube:*:*:*:*:*:*:*:* |
Original advisory text
MyTube has Unauthenticated Account Lockout via Shared Login Attempt State
MyTube is a self-hosted downloader and player for several video websites Prior to version 1.8.72, an unauthenticated attacker can lock out administrator and visitor accounts from password-based authentication by triggering failed login attempts. The application exposes three password verification endpoints, all of which are publicly accessible. All three endpoints share a single file-backed login attempt state stored in `login-attempts.json`. When any endpoint records a failed authentication attempt via `recordFailedAttempt()`, the shared login attempt state is updated, increasing the `failedAttempts` counter and adjusting the associated timestamps and cooldown values. Before verifying a password, each endpoint calls `canAttemptLogin()`. This function checks the shared JSON file to determine whether a cooldown period is active. If the cooldown has not expired, the request is rejected before the password is validated. Because the failed attempt counter and cooldown timer are globally shared, failed authentication attempts against any endpoint affect all other endpoints. An attacker can exploit this by repeatedly sending invalid authentication requests to any of these endpoints, incrementing the shared counter and waiting for the cooldown period between attempts. By doing so, the attacker can progressively increase the lockout duration until it reaches 24 hours, effectively preventing legitimate users from authenticating. Once the maximum lockout is reached, the attacker can maintain the denial of service indefinitely by waiting for the cooldown to expire and sending another failed attempt, which immediately triggers another 24-hour lockout if no successful login occurred in the meantime. Version 1.8.72 fixes the vulnerability.
References
- https://github.com/franklioxygen/MyTube/blob/941035909ee3f96a6f80f38acf70cbc3e66... URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33935... Vendor Advisory
- https://github.com/franklioxygen/MyTube/security/advisories/GHSA-6w95-qgc4-5jxf Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-33935 Vendor Advisory
- https://github.com/franklioxygen/MyTube/commit/4d89b146b16d08f27d8fd3e0a9122b109... Patch
- https://github.com/franklioxygen/MyTube/commit/752bc7f0ac83df8c881e6b6d5dd6f36bb... Patch
- https://github.com/franklioxygen/MyTube/commit/dd7b4a611fcc5b25a569f379be9a503eb... Patch
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
8.3
High
Type
CWE-307Improper Restriction of Excessive Authentication Attempts
Timeline
Published27 Mar 2026
Updated4 Nov 2026
First seen27 Mar 2026
Track software like this
Free during beta