CVE-2026-27707: CWE-288: Authentication Bypass Using an Alternate Path or Channel in seerr-team seerr
Seerr is an open-source media request and discovery manager for Jellyfin, Plex, and Emby. Starting in version 2.0.0 and prior to version 3.1.0, an authentication guard logic flaw in `POST /api/v1/auth/jellyfin` allows an unauthenticated attacker to register a new Seerr account on any Plex-configured instance by authenticating with an attacker-controlled Jellyfin server. The attacker receives an authenticated session and can immediately use the application with default permissions, including the ability to submit media requests to Radarr/Sonarr. Any Seerr deployment where all three of the following are true may be vulnerable: `settings.main.mediaServerType` is set to `PLEX` (the most common deployment).; `settings.jellyfin.ip` is set to `""` (default, meaning Jellyfin was never configured); and `settings.main.newPlexLogin` is set to `true` (default). Jellyfin-configured and Emby-configured deployments are not affected. Version 3.1.0 of Seerr fixes this issue.
AI Analysis
Technical Summary
Seerr is an open-source media request and discovery manager integrating with media servers like Jellyfin, Plex, and Emby. The vulnerability CVE-2026-27707 arises from an authentication guard logic flaw in the POST /api/v1/auth/jellyfin endpoint. Specifically, when Seerr is configured to use Plex as its media server type (settings.main.mediaServerType = PLEX), with Jellyfin IP unset (settings.jellyfin.ip = ""), and new Plex login enabled (settings.main.newPlexLogin = true), an attacker can bypass authentication. The attacker sets up a malicious Jellyfin server and tricks Seerr into authenticating against it, allowing the attacker to register a new Seerr account without valid credentials. This results in an authenticated session with default user permissions, permitting the attacker to interact with the application, including submitting media requests to Radarr and Sonarr. The flaw is due to improper validation of the authentication source and failure to enforce correct authentication channels. The vulnerability affects all Seerr versions from 2.0.0 up to 3.1.0 and is fixed in version 3.1.0. The CVSS 3.1 score of 7.3 indicates a high-severity issue exploitable remotely without authentication or user interaction, impacting confidentiality, integrity, and availability of the system. No public exploits have been reported yet, but the ease of exploitation and potential impact warrant prompt remediation.
Potential Impact
Organizations running Seerr versions between 2.0.0 and 3.0.x with Plex configured and default Jellyfin settings are at risk of unauthorized access. An attacker can gain authenticated sessions without credentials, potentially leading to unauthorized media requests and manipulation of integrated services like Radarr and Sonarr. This could result in resource misuse, exposure of media request data, and disruption of media management workflows. While the default permissions limit the attacker's capabilities, the breach of authentication undermines system integrity and confidentiality. Additionally, attackers could use this foothold to pivot within the network or escalate privileges if other vulnerabilities exist. Media server environments in home, small business, or community settings relying on Seerr for media management are particularly vulnerable. The vulnerability does not require user interaction and can be exploited remotely, increasing the risk of widespread attacks if unpatched.
Mitigation Recommendations
Upgrade Seerr to version 3.1.0 or later, where this authentication bypass vulnerability is fixed. For environments where immediate upgrade is not feasible, administrators should disable the new Plex login feature (settings.main.newPlexLogin = false) to prevent the vulnerable authentication path. Additionally, explicitly configure the Jellyfin IP setting (settings.jellyfin.ip) to a valid, trusted address rather than leaving it blank to avoid fallback to insecure defaults. Network-level controls should restrict access to the Seerr API endpoints, allowing only trusted clients and servers. Monitoring and logging authentication attempts to detect unusual or unauthorized registrations can help identify exploitation attempts. Finally, review and harden integration points with Radarr and Sonarr to limit the impact of unauthorized requests, including applying least privilege principles and validating incoming requests.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, Sweden, Norway, Japan, South Korea
CVE-2026-27707: CWE-288: Authentication Bypass Using an Alternate Path or Channel in seerr-team seerr
Description
Seerr is an open-source media request and discovery manager for Jellyfin, Plex, and Emby. Starting in version 2.0.0 and prior to version 3.1.0, an authentication guard logic flaw in `POST /api/v1/auth/jellyfin` allows an unauthenticated attacker to register a new Seerr account on any Plex-configured instance by authenticating with an attacker-controlled Jellyfin server. The attacker receives an authenticated session and can immediately use the application with default permissions, including the ability to submit media requests to Radarr/Sonarr. Any Seerr deployment where all three of the following are true may be vulnerable: `settings.main.mediaServerType` is set to `PLEX` (the most common deployment).; `settings.jellyfin.ip` is set to `""` (default, meaning Jellyfin was never configured); and `settings.main.newPlexLogin` is set to `true` (default). Jellyfin-configured and Emby-configured deployments are not affected. Version 3.1.0 of Seerr fixes this issue.
AI-Powered Analysis
Technical Analysis
Seerr is an open-source media request and discovery manager integrating with media servers like Jellyfin, Plex, and Emby. The vulnerability CVE-2026-27707 arises from an authentication guard logic flaw in the POST /api/v1/auth/jellyfin endpoint. Specifically, when Seerr is configured to use Plex as its media server type (settings.main.mediaServerType = PLEX), with Jellyfin IP unset (settings.jellyfin.ip = ""), and new Plex login enabled (settings.main.newPlexLogin = true), an attacker can bypass authentication. The attacker sets up a malicious Jellyfin server and tricks Seerr into authenticating against it, allowing the attacker to register a new Seerr account without valid credentials. This results in an authenticated session with default user permissions, permitting the attacker to interact with the application, including submitting media requests to Radarr and Sonarr. The flaw is due to improper validation of the authentication source and failure to enforce correct authentication channels. The vulnerability affects all Seerr versions from 2.0.0 up to 3.1.0 and is fixed in version 3.1.0. The CVSS 3.1 score of 7.3 indicates a high-severity issue exploitable remotely without authentication or user interaction, impacting confidentiality, integrity, and availability of the system. No public exploits have been reported yet, but the ease of exploitation and potential impact warrant prompt remediation.
Potential Impact
Organizations running Seerr versions between 2.0.0 and 3.0.x with Plex configured and default Jellyfin settings are at risk of unauthorized access. An attacker can gain authenticated sessions without credentials, potentially leading to unauthorized media requests and manipulation of integrated services like Radarr and Sonarr. This could result in resource misuse, exposure of media request data, and disruption of media management workflows. While the default permissions limit the attacker's capabilities, the breach of authentication undermines system integrity and confidentiality. Additionally, attackers could use this foothold to pivot within the network or escalate privileges if other vulnerabilities exist. Media server environments in home, small business, or community settings relying on Seerr for media management are particularly vulnerable. The vulnerability does not require user interaction and can be exploited remotely, increasing the risk of widespread attacks if unpatched.
Mitigation Recommendations
Upgrade Seerr to version 3.1.0 or later, where this authentication bypass vulnerability is fixed. For environments where immediate upgrade is not feasible, administrators should disable the new Plex login feature (settings.main.newPlexLogin = false) to prevent the vulnerable authentication path. Additionally, explicitly configure the Jellyfin IP setting (settings.jellyfin.ip) to a valid, trusted address rather than leaving it blank to avoid fallback to insecure defaults. Network-level controls should restrict access to the Seerr API endpoints, allowing only trusted clients and servers. Monitoring and logging authentication attempts to detect unusual or unauthorized registrations can help identify exploitation attempts. Finally, review and harden integration points with Radarr and Sonarr to limit the impact of unauthorized requests, including applying least privilege principles and validating incoming requests.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-23T17:56:51.203Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a1f35732ffcdb8a26a774e
Added to database: 2/27/2026, 7:41:11 PM
Last enriched: 2/27/2026, 7:55:27 PM
Last updated: 2/28/2026, 3:45:46 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2024-29741: Elevation of privilege in Google Android
HighCVE-2026-28426: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
HighCVE-2025-11252: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Signum Technology Promotion and Training Inc. windesk.fm
CriticalCVE-2026-2647
UnknownCVE-2026-28425: CWE-94: Improper Control of Generation of Code ('Code Injection') in statamic cms
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.