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

Published Sep 18, 2026
·
Updated

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

1 affected component
Kyoo<5.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Kyoo to a version that resolves this vulnerability.

    Fixed in 5.1.0

Event History

Sep 18, 2026
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

What is the available remediation?

Upgrade Kyoo to version 5.1.0, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203