Bazarr 1.6.2 upgrade: security fixes, no breaking changes found
Summary
Bazarr 1.6.2 is mostly fixes and hardening, with a few new options. The release notes list:
- Post-processing commands are now passed as an argument list instead of one command string. The notes say this prevents shell injection and fixes Windows path handling.
- Subtitle deletion now checks that the subtitle exists in the database first. The notes say this prevents unauthorized file deletion.
- Duplicate entries in episode and movie subtitle history are fixed (#3558).
- Cutoff logic now correctly counts non-HI subtitles when HI is excluded in a language profile, for series and movies (#3607).
- New: anime provider tsukihime, a hash-only mode for napiprojekt (which now uses SSL), more URL parameters on the generic webhook, and quality-check settings for subsync’s framerate-fix mode (minimum score, max offset, max framerate deviation).
- Smaller fixes: subssabbz fallback for non-ASCII titles, and the mass-edit checkbox being disabled for non-srt formats.
Breaking changes and deprecations
The release notes list no breaking changes. One change could matter if you use post-processing: commands are now run as an argument list, not through a shell. If your post-processing command relies on shell features (pipes, &&, redirects), check it after upgrading. We did not test this. It is our reading of the release note, not something we confirmed.
Tested in our lab
Tested: a Docker upgrade from 1.6.1 to 1.6.2 using the LinuxServer.io image.
- Started 1.6.1 with Docker Compose and confirmed the API answered.
- Changed a setting (
general.page_sizefrom 25 to 50) so there was config data to check. - Stopped the container with
docker compose down, changed the image tag toversion-v1.6.2, pulled it and started it again. - After the upgrade, the API reported 1.6.2. The web UI answered with HTTP 200. The changed setting was still 50. The container log contained no lines matching “error”, “traceback” or “exception”.
Not tested: Sonarr/Radarr integration, subtitle providers, post-processing, subtitle deletion, subsync, webhooks and history. The lab instance had no media library, so none of the 1.6.2 fixes were exercised. This test shows only that the upgrade works and the config survives.
Lab log
$ docker compose up -d
Container bazarr Started
$ curl -s -H "X-API-KEY: [redacted]" localhost:6767/api/system/status
{"data": {"bazarr_version": "1.6.1", "package_version": "v1.6.1-ls365 by linuxserver.io", [...]
$ curl -s -X POST -H "X-API-KEY: [redacted]" -d "settings-general-page_size=50" -w "%{http_code}\n" localhost:6767/api/system/settings
204
$ docker compose down
Container bazarr Removed
Network bazarr_default Removed
$ sed -i "s/version-v1.6.1/version-v1.6.2/" compose.yaml
$ docker compose pull
Image lscr.io/linuxserver/bazarr:version-v1.6.2 Pulled
$ docker compose up -d
Container bazarr Started
$ curl -s -H "X-API-KEY: [redacted]" localhost:6767/api/system/status | grep -o "\"bazarr_version\": \"[^\"]*\"\|\"package_version\": \"[^\"]*\""
"bazarr_version": "1.6.2"
"package_version": "v1.6.2-ls370 by linuxserver.io"
$ curl -s -H "X-API-KEY: [redacted]" localhost:6767/api/system/settings | grep -o "\"page_size\":[^,]*"
"page_size":50
$ curl -s -o /dev/null -w "ui %{http_code}\n" localhost:6767/
ui 200
$ docker logs bazarr 2>&1 | grep -ciE "error|traceback|exception"
0
Reported by others
We did not look through issues or forums for upgrade reports. The items above come from the official release notes.
Verdict
Upgrade now, especially if you use post-processing scripts or expose Bazarr to others. The security-related changes are worth having, and the upgrade from 1.6.1 was clean in our lab. Back up your /config folder first, as you would for any upgrade. If you use post-processing, run a test afterwards because of the argument-list change.