External risk intelligence

Bazarr Path Traversal and Arbitrary File Write Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130156

Bazarr is a companion application designed for local media management. While it is a web-based service that can be exposed to the internet if configured by a user to be remotely accessible, it is typically deployed as a local or private internal service for media library management rather than a public-facing edge or gateway service.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in Bazarr, a media management application. This issue could allow unauthorized access to read and potentially overwrite files outside of its intended media library, depending on the application's configuration and the permissions of the user running the Bazarr process. The primary concern at this time is to confirm if Bazarr is deployed in a manner that could expose it to this risk.

  • Unrestricted file access within Bazarr.
  • Confirms potential for unauthorized file modification.
  • Verify if Bazarr is deployed to warrant further review.

Attack Path

How an attacker could exploit the issue

An attacker could gain access to sensitive files outside of Bazarr's media library by exploiting a path traversal vulnerability. This could occur if API authentication is disabled or if the attacker can bypass authentication. The vulnerability allows an attacker to trick Bazarr into reading arbitrary files on the system, and potentially overwrite them, limited only by the permissions of the Bazarr process.

  • No authentication or bypassed authentication.
  • Malicious path in API request.
  • Read and overwrite arbitrary files.

Live Threat

Current exploitation, exposure, and threat context

When Bazarr's API authentication is disabled, an unauthenticated attacker could exploit this vulnerability to read or write files outside of the Bazarr media library, provided the Bazarr process has the necessary permissions for those files. This could potentially impact system data or allow for unauthorized modifications to files the application can access.

  • System files accessible by Bazarr.
  • Path traversal via API requests.
  • Unauthorized file reads or writes.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for addressing this vulnerability, as Bazarr interacts with files on the local system where it's deployed. The initial step is to locate all instances of Bazarr, determine their exposure (internal vs. external), confirm business criticality, and identify the accountable system owner before planning remediation.

  • Identify affected Bazarr instances and ownership.
  • Verify file path traversal exposure and impact.
  • Plan remediation or risk mitigation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Bazarr and how is it typically used?

Bazarr is a companion application that automates the downloading and management of subtitles for media libraries. It works alongside tools like Sonarr and Radarr to ensure users have the correct subtitle files for their movies and TV shows. By integrating with these media automation platforms, it handles the ongoing process of finding and syncing subtitle contents based on the library files a user maintains.

What is the vulnerability in CVE-2026-130156?

This vulnerability is classified as Improper Limitation of a Pathname to a Restricted Directory, or path traversal (CWE-22). It means the application fails to properly validate file paths provided by a user. Instead of restricting operations to the intended media library folder, the application can be tricked into reading or overwriting files anywhere on the system that the Bazarr process itself has permission to access.

How does an attacker trigger this bug?

An attacker triggers this by sending specially crafted requests to the application's API endpoints that handle subtitle information or synchronization. If API authentication is disabled or bypassed, the application processes these requests without verifying if the requested file path resides within authorized directories. Notably, simple extension checks are insufficient to stop this, as the core logic flaw allows accessing unauthorized file locations.

Do I need to worry if my Bazarr instance is internal?

Halo Surface Signal indicates that Bazarr is typically deployed as a local or private service, which reduces general exposure compared to public-facing edge services. However, if your configuration makes the service remotely accessible, the risk increases. You should evaluate whether your instance is reachable over the internet or if it is strictly restricted to your internal network, as network-based access is the primary vector.

What is the first step to address this CVE?

The most effective way to secure your environment is to update Bazarr to version 1.6.3-beta.11 or later, which contains the necessary path validation fixes. Before updating, you should identify all running instances, confirm whether API authentication is currently enabled, and assess if the service is exposed to networks you do not control to prioritize your mitigation efforts.

References