# CVE-2026-130156: Path traversal in bazarr

> Attackers, unauthenticated when API auth is disabled, can read and write arbitrary files via Bazarr subtitle endpoints; Bazarr operators should care.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-2876-64fx-p4m9

## What is CVE-2026-130156?

CVE-2026-130156 is a critical path traversal vulnerability in morpheus65535 bazarr, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bazarr is a companion application to Sonarr and Radarr. Prior to 1.6.3-beta.11, the /api/subtitles/subtitles-info handler uses SubtitleNameContents.get() in subtitles_contents.py and reads the caller-supplied subtitlePath after checking only its subtitle extension; because the resolved path is not confined to files indexed by Bazarr, traversal can read files outside the media library. The /api/subtitles/subtitles handler in subtitles.py passes caller-supplied path and reference to sync and translation without per-path authorization, allowing an out-of-library reference file to be read and output to overwrite a file outside the media library. The authenticate decorator gates both endpoints when API authentication is enabled, while auth = None allows access without credentials. Both paths can affect only files that the Bazarr process can read or write. This issue is fixed in version 1.6.3-beta.11.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-130156?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-130156?

No fix has been published for CVE-2026-130156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130156 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130156 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130156 and fix it if it is affected.

What it is: CVE-2026-130156 is a critical path traversal vulnerability in morpheus65535 bazarr, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130156 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: morpheus65535 bazarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130156/ (Markdown: https://insights.sbomify.com/CVE-2026-130156/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130156
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130156
- OSV: https://osv.dev/vulnerability/CVE-2026-130156

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130156/
Summaries are generated and may contain mistakes; the official description above is the record.
