CVE-2026-23848VulnerabilityPublished 19 Jan 2026

CVE-2026-23848: franklioxygen MyTube · Reliance on Untrusted Inputs in a Security Decision

Affects franklioxygen MyTubeSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.7.71 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.7.71

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade MyTube and franklioxygen/MyTube to 1.7.71.

Affected software

Product	Affected	Fixed in
franklioxygenMyTube	Affected <1.7.71	Fixed in 1.7.71
GitHubfranklioxygen/MyTube`pkg:github/franklioxygen/MyTube`Other threats	Affected <1.7.71	Fixed in 1.7.71

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade MyTube installations to version 1.7.71 or later, where the vulnerability is patched. If upgrading is not immediately feasible, implement network-level controls to validate or strip the X-Forwarded-For header from incoming requests before they reach MyTube, ensuring that spoofed headers cannot influence rate limiting. Deploy Web Application Firewalls (WAFs) or reverse proxies configured to enforce rate limiting based on trusted client IPs or other reliable identifiers rather than headers that can be spoofed. Monitor API usage patterns for unusual spikes in request rates that may indicate exploitation attempts. Restrict access to MyTube API endpoints to trusted networks or VPNs where possible to reduce exposure. Conduct regular security audits and penetration tests focusing on header manipulation and rate limiting controls. Maintain up-to-date incident response plans to quickly address potential DoS attacks. Finally, educate administrators about the risks of trusting client-supplied headers for security decisions.

Description

CVE-2026-23848 is a medium severity vulnerability in franklioxygen's MyTube versions prior to 1.7.71. It allows unauthenticated attackers to bypass IP-based rate limiting by spoofing the X-Forwarded-For header, enabling unlimited requests to API endpoints. This can lead to denial-of-service conditions and abuse of rate-limited functionality. The vulnerability arises from reliance on untrusted input for security decisions (CWE-807). No authentication or user interaction is required, and the vulnerability affects availability primarily, with limited confidentiality impact. A patch was released in version 1.7.71 to address this issue.

Impact

For European organizations using MyTube versions prior to 1.7.71, this vulnerability poses a risk of denial-of-service attacks that can disrupt access to video downloading and playback services. This could affect internal workflows relying on MyTube for media consumption or content processing, especially in media companies, educational institutions, or enterprises with self-hosted media solutions. The ability to bypass rate limits without authentication increases the risk of automated abuse, potentially leading to service outages or degraded performance. While confidentiality and integrity impacts are limited, availability disruptions could affect business continuity and user satisfaction. Organizations operating in sectors where video content delivery is critical may face operational and reputational damage. Additionally, if MyTube is exposed to the internet, attackers could exploit this vulnerability remotely without authentication, increasing the attack surface. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

CWE-807Reliance on Untrusted Inputs in a Security Decision (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
Architecture and Design · Attack Surface Reduction
Store state information and sensitive data on the server side only.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 20:23 UTC

WeaknessesCWE-807

Technical details

References

Community reviews

Related threats