CVE
Bazarr arbitrary file read and write in subtitle endpoints
Affects Bazarr 1.6.3-beta.10 and earlier when API authentication is disabled (auth = None). Fixed in 1.6.3-beta.11. CVSS scores it 9.4, critical.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.6.3-beta.11
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.6.3-beta.11.
Summary
Bazarr, a companion application to Sonarr and Radarr, has a path traversal flaw in its subtitle endpoints that lets an attacker read files outside the media library and overwrite files the Bazarr process can write to. An attacker can reach it remotely, without logging in, through the subtitle API.
Original 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.
Who should check
Anyone running Bazarr 1.6.3-beta.10 or earlier with API access, including instances with auth = None.
“<= 1.6.3-beta.10”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.6.3-beta.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130156 (Bazarr: Authenticated path traversal (arbitrary file read & write) in subtitle operations due to missing path containment), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130156 (entry last updated 2026-11-18):
Affected:
- morpheus65535 bazarr: fixed in 1.6.3-beta.11
Fixed versions: 1.6.3-beta.11.
Conditions (all must be true for the bug to be hit):
- Bazarr 1.6.3-beta.10 or earlier (source: https://github.com/morpheus65535/bazarr/security/advisories/GHSA-2876-64fx-p4m9)
- API authentication disabled (auth = None), so access needs no credentials (source: https://github.com/morpheus65535/bazarr/security/advisories/GHSA-2876-64fx-p4m9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130156 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130156 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/morpheus65535/bazarr/security/advisories/GHSA-2876-64fx-p4m9
- https://github.com/morpheus65535/bazarr/commit/d84777c61a34a90a37238cfb566e7e8cd102d303
- https://github.com/morpheus65535/bazarr/releases/tag/v1.6.3-beta.11
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130156
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130156"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- morpheus65535 bazarr
fixed in 1.6.3-beta.11
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · morpheus65535/bazarr · Advisory GHSA-2876-64fx-p4m9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130156 |
| Record | NVD · CVE-2026-130156 |
| Other links 2 | |
| Repository | GitHub · morpheus65535/bazarr · Commit d84777c6 |
| Repository | GitHub · morpheus65535/bazarr · Release v1.6.3-beta.11 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130156
Is CVE-2026-130156 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Subtitle operations in Bazarr do not contain file paths to the media library, so a request can read arbitrary subtitle-extension files on the host and overwrite arbitrary files writable by the Bazarr process.Source: github.com
Which versions are affected by CVE-2026-130156?
bazarr: before 1.6.3-beta.11.Source: cve.now feed data
Am I affected, and how do I check?
Bazarr 1.6.3-beta.10 and earlier are in scope, and the setup matters: the flaw applies when API authentication is disabled (auth = None), where any user can reach it without credentials. Check the installed Bazarr version and the auth setting in its configuration.Source: github.com
How do I fix CVE-2026-130156?
Upgrade Bazarr to 1.6.3-beta.11 or later.Source: github.com