CVE-2026-77386: Kyoo: OIDC login token can be redirected to an attacker-controlled URL
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kyooto a version that resolves this vulnerability.Fixed in 5.1.0
Event History
Frequently Asked Questions
Which Kyoo deployments are exposed?
Kyoo versions prior to 5.1.0 are affected when OIDC login is available and users can be induced to complete an OIDC authentication flow.
Does exploitation require an attacker account or prior access?
No. An unauthenticated attacker can initiate the OIDC login flow, but must induce a victim to complete OIDC authentication and receive the redirected token at an attacker-controlled destination.
What is the available remediation?
Upgrade Kyoo to version 5.1.0, which fixes the issue.