Quick answers
- Is CVE-2026-63433 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63433 being exploited in the wild.
- How severe is CVE-2026-63433?
- Medium severity, with a CVSS score of 6.8, published 3 November 2026.
- Which products and versions are affected?
- Franklioxygen MyTube prior to 1.10.6.
- Is there a fix for CVE-2026-63433?
- Yes: fixed in 1.10.6. Until then: Restrict CORS_ALLOWED_ORIGINS to a narrow allowlist of trusted origins rather than permissive values like "*"; do not use broad domain wildcards in cross-origin configurations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63433 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-63433?
- Check whether you run Franklioxygen MyTube at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.10.6
Restrict CORS_ALLOWED_ORIGINS to a narrow allowlist of trusted origins rather than permissive values like "*"; do not use broad domain wildcards in cross-origin configurations.
Technical details
The vulnerability exists in the CSRF middleware's shouldSkipCsrfProtection() function, which delegates to isApiKeyRequest() that checks only for the presence of an x-api-key or Authorization: ApiKey header without validating the key's actual value. This causes CSRF token validation to be skipped for any request bearing these headers, even with bogus values. An attacker can exploit this via a cross-origin request when CORS allows the attacker's origin, as the victim's session cookie authenticates the forged request after the CSRF gate has been opened.
Affected products
- franklioxygen MyTube prior to 1.10.6
Timeline
- 2026-07-01: disclosed
- 2026-11-03: advisory