CVE-2026-77386

Kyoo: OIDC login token can be redirected to an attacker-controlled URL

Published Sep 18, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Kyoo is a self-hosted media server focused on movies, series, and anime. Prior to 5.1.0, an unauthenticated attacker could initiate the OIDC login flow with an attacker-controlled redirectUrl. The login handling in auth/oidc.go stored that URL with the opaque login state, and /auth/oidc/logged/{provider} appended the provider, token, and error values before redirecting the victim's browser without validating the destination. Because the one-use token was not bound to the browser session that initiated login, an attacker who induced a victim to complete OIDC authentication could capture the token at the attacker-controlled destination and exchange it through /auth/oidc/callback/{provider} for the victim's Kyoo session. This issue is fixed in version 5.1.0.

Analysis

AI-generated

Technical impact

Prior to Kyoo version 5.1.0, an attacker could initiate the OIDC authentication flow using a malicious redirect URL. The authentication handler stored the redirect without validation, allowing the attacker to capture the user’s token when the victim completed authentication. The attacker could then exchange that token for a Kyoo session, effectively hijacking the victim’s account. This flaw, an instance of CWE‑601, enables unauthorized access to a user’s media server without needing to compromise the server directly.

Affected Systems

The vulnerability affects the Kyoo media server developed by zoriya. All releases before version 5.1.0 are compromised; version 5.1.0 and later contain the fix.

Risk and Exploitability

The CVSS score of 6.5 reflects a medium severity risk. The EPSS score is not available and the issue is not listed in the CISA KEV catalog. Exploitation requires an unauthenticated attacker to persuade a victim to complete the OIDC flow with a crafted redirect URL. Because the one‑use token is not tied to the initiating browser session, the attacker can capture it and trade it for a valid Kyoo session, resulting in account takeover. The vulnerability does not provide remote code execution, but it permits hijacking of user sessions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kyoo to version 5.1.0 or later to apply the official fix
  • If OIDC authentication is not required, disable it or restrict it to trusted domains
  • Validate all redirect URLs in the authentication flow to prevent open redirect redirects

Generated by OpenCVE AI on September 19, 2026 at 11:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zoriya
Zoriya kyoo
Vendors & Products Zoriya
Zoriya kyoo
Type Values Removed Values Added
Description Kyoo is a self-hosted media server focused on movies, series, and anime. Prior to 5.1.0, an unauthenticated attacker could initiate the OIDC login flow with an attacker-controlled redirectUrl. The login handling in auth/oidc.go stored that URL with the opaque login state, and /auth/oidc/logged/{provider} appended the provider, token, and error values before redirecting the victim's browser without validating the destination. Because the one-use token was not bound to the browser session that initiated login, an attacker who induced a victim to complete OIDC authentication could capture the token at the attacker-controlled destination and exchange it through /auth/oidc/callback/{provider} for the victim's Kyoo session. This issue is fixed in version 5.1.0.
Title Kyoo: OIDC login token can be redirected to an attacker-controlled URL
Weaknesses CWE-601
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-601

    URL Redirection to Untrusted Site ('Open Redirect')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 22, 2026, 3:09 PM
Reserved
Aug 20, 2026, 7:36 PM
Status
Deferred
Published
Sep 18, 2026, 6:17 PM
Modified
Sep 24, 2026, 9:25 PM