Is CVE-2026-61826 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61826 being exploited in the wild.

How severe is CVE-2026-61826?

Critical severity, with a CVSS score of 10, published 30 October 2026.

Is there a fix for CVE-2026-61826?

Yes: fixed in 1.5.7-beta.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61826 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-61826?

Check whether you run Bazarr 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.

CVE-2026-61826: Bazarr Plex OAuth authentication bypass

CVE-2026-61826 · Severity: critical · CVSS 10 · Published 2026-10-30

Bazarr is a subtitle management tool for media servers that integrates with Plex for authentication. Prior to version 1.5.7-beta.14, the Plex OAuth API endpoints lack authentication requirements, allowing unauthenticated attackers to clear credentials, inject malicious API keys, and manipulate server configuration. This enables an attacker to disable the Plex integration, conduct server-side request forgery attacks, or expose API credentials stored in the application.

Quick answers

Is CVE-2026-61826 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61826 being exploited in the wild.
How severe is CVE-2026-61826?: Critical severity, with a CVSS score of 10, published 30 October 2026.
Which products and versions are affected?: Bazarr prior to 1.5.7-beta.14.
Is there a fix for CVE-2026-61826?: Yes: fixed in 1.5.7-beta.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61826 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-61826?: Check whether you run Bazarr 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.5.7-beta.14

Technical details

The `api_ns_plex` namespace in `bazarr/api/plex/oauth.py` omits `@authenticate` decorators on Resource handlers, while other APIs require API keys. Multiple endpoints (`POST /api/plex/oauth/logout`, `POST /api/plex/apikey`, `POST /api/plex/oauth/pin`, `GET /api/plex/oauth/pin/<pin_id>/check`, and others) allow unauthenticated callers to perform write operations including credential manipulation and configuration changes. Additionally, `PlexPinCheck` skips state validation when absent, and attacker-controlled Plex server URLs in configuration feed into outbound requests carrying the API key in the `X-Plex-Token` header, enabling SSRF and credential exposure.

Affected products

Bazarr Bazarr prior to 1.5.7-beta.14

Timeline

2026-10-30: disclosed
2026-10-30: patched: Fixed in version 1.5.7-beta.14

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.