SABnzbd 5.1.3 upgrade: 5 security fixes, no breaking changes

released
lab run
upgraded from
5.1.2
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

SABnzbd 5.1.3 is mainly a security release. It completes a series of fixes that started in 5.1.1 and 5.1.2. Two issues are fixed in 5.1.3 itself:

  • GHSA-q326-jpxx-jmjc: a __wrapped__ dispatch bypass allowed unauthenticated API access.
  • GHSA-mjwj-v5mr-cmcg: a PAR2 symlink bypass allowed remote code execution through a pickle file.

Other changes are small: a tighter Compact display mode, usenet server errors shown directly, a fix for a database is locked error when re-evaluating stored RSS jobs, and a tooltip explaining the search filters in Queue and History.

Breaking changes and deprecations

None listed for 5.1.3. The release notes say you can upgrade directly from 3.0.0 or newer; older versions need a Queue repair.

Tested in our lab

We ran SABnzbd 5.1.2 in Docker (linuxserver image), created a test category through the API, then stopped the container, removed it and started 5.1.3 on the same config and download volumes.

  • The container came up and the API reported 5.1.3.
  • The category created before the upgrade was still there.
  • The web UI answered (HTTP 303 redirect on /).
  • No errors or warnings in the container log.

We did not test the security fixes themselves, did not test downloading or Usenet servers, and did not test the RSS changes.

Lab log

$ docker run -d --name sabnzbd -p 8080:8080 -v /srv/sab/config:/config -v /srv/sab/downloads:/downloads lscr.io/linuxserver/sabnzbd:5.1.2
$ curl -s "http://localhost:8080/api?mode=version&output=json"
{"version":"5.1.2"}
$ curl -s "http://localhost:8080/api?mode=set_config&section=categories&name=testcat&dir=testcat&apikey=[redacted]&output=json"
{"config":{"categories":[{"name":"testcat","order":0,"pp":"","script":"Default","dir":"testcat","newzbin":"","priority":-100}]}}
$ docker stop sabnzbd
sabnzbd
$ docker rm sabnzbd
sabnzbd
$ docker run -d --name sabnzbd -p 8080:8080 -v /srv/sab/config:/config -v /srv/sab/downloads:/downloads lscr.io/linuxserver/sabnzbd:5.1.3
$ docker ps --format "{{.Names}} {{.Image}} {{.Status}}"
sabnzbd lscr.io/linuxserver/sabnzbd:5.1.3 Up 25 seconds
$ curl -s "http://localhost:8080/api?mode=version&output=json"
{"version":"5.1.3"}
$ curl -s "http://localhost:8080/api?mode=get_cats&apikey=[redacted]&output=json"
{"categories":["*","testcat","movies","tv","audio","software"]}
$ curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8080/
303
$ docker logs sabnzbd 2>&1 | grep -iE "error|warn|traceback"

Reported by others

From the SABnzbd vulnerability page and release notes (not tested by us):

  • GHSA-q326-jpxx-jmjc (unauthenticated API access): affects 5.1.2 and earlier. Only matters if the web interface is reachable by untrusted parties.
  • GHSA-mjwj-v5mr-cmcg (PAR2 symlink, RCE): affects 5.1.2 and earlier, mainly Unix-like systems. It needs a malicious download, so it matters if you take NZBs from sources you don’t trust. No mitigation other than updating.
  • GHSA-rgqj-28c2-gxwp (RCE via config endpoints, fixed in 5.1.2), GHSA-75g3-96fr-7p2r (PAR2/SFV path traversal, fixed in 5.1.2) and GHSA-xrfq-jhgh-wqch (session auth bypass, fixed in 5.1.1).
  • By default SABnzbd is only reachable from the local device and External internet access is No access, so default setups are not exposed to the web interface issues.
  • If your web interface was reachable by someone you don’t trust, the project recommends rotating your SABnzbd username/password and API key, Usenet server passwords, indexer API keys used in RSS feeds, and notification credentials after updating.

Verdict

Upgrade now. The fixes are important if you expose SABnzbd or download from public indexers, and the upgrade from 5.1.2 in Docker needed no extra steps in our test. If you skipped 5.1.1 or 5.1.2, read the earlier fixes above and consider rotating credentials.

sources