qBittorrent 5.3.0 upgrade: WebUI security fixes, few breaking changes

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

Summary

qBittorrent 5.3.0 is a large feature release with about 120 listed changes. Most are features and bug fixes. The ones that matter for home servers are the security fixes in the WebUI and email code, listed below.

Breaking changes and deprecations

The release notes do not have a “breaking changes” section. These items can change behaviour (all reported in the release notes, not all tested by us):

  • WebAPI: search/downloadTorrent and rss/setFeedRefreshInterval now require POST (#24791). Scripts that use GET will break.
  • WebUI: cross-site requests are now detected with the Sec-Fetch-Site header (#24792, #24970). Reverse-proxy setups may notice this.
  • WebUI: “server domain” matching is now anchored (#24458). Check your domain setting if you use it.
  • WebUI: a limit on the number of sessions was added (#24720).
  • “Resolve peer countries” is now off by default, for new installs only (#24505).
  • The minimum Python version for the search engine was raised (#24279).
  • Some outdated setting keys were removed (#23952).

Tested in our lab

We ran qBittorrent in Docker (qbittorrentofficial/qbittorrent-nox), first at 5.2.4, then upgraded to 5.3.0.

  • Before the upgrade we changed the max connections setting to 321 and added one magnet link in a category called lab.
  • We stopped the container with docker compose down, changed the image tag, pulled it and started it again with the same ./config and ./downloads volumes.
  • After the upgrade the WebAPI reported v5.3.0, the torrent and its category were still there, and the max connections setting was still 321.
  • A request with a spoofed X-Forwarded-For header and no login got HTTP 403.
  • A GET to search/downloadTorrent returned 405 Method Not Allowed, matching the release notes.
  • A search of the container log for “error” or “warn” after the upgrade printed nothing.
  • Not tested: downloading data, RSS, email notifications, search plugins, the desktop app, and Windows or macOS builds.

The container prints a new temporary admin password on each start if you have not set one. Set your own password in the WebUI.

Lab log

$ docker compose up -d
$ curl -s -b j http://localhost:8080/api/v2/app/version
v5.2.4
$ docker compose down
$ sed -i "s/5.2.4-1/5.3.0-2/" compose.yaml
$ docker compose pull
$ docker compose up -d
$ curl -s -b j http://localhost:8080/api/v2/app/version
v5.3.0
$ curl -s -b j http://localhost:8080/api/v2/torrents/info | grep -o "\"name\":\"[^\"]*\"\|\"category\":\"[^\"]*\""
"category":"lab"
"name":"Big Buck Bunny"
$ curl -s -b j http://localhost:8080/api/v2/app/preferences | grep -o "\"max_connec\":[0-9]*"
"max_connec":321
$ curl -s -o /dev/null -w "%{http_code}\n" -H "X-Forwarded-For: 1.2.3.4" http://localhost:8080/api/v2/app/version
403
$ curl -s -b j -w " %{http_code}\n" "http://localhost:8080/api/v2/search/downloadTorrent?torrentUrl=x&pluginName=y"
Method Not Allowed 405

Reported by others

From the release notes, not tested by us:

  • Fix for an authentication bypass through X-Forwarded-For spoofing (#24889).
  • Fix for SMTP injection from unsanitized mail content (#24793) and a STARTTLS fix (#23838).
  • Dynamic DNS now uses HTTPS (#24805).
  • Announces from unauthenticated sources no longer create a torrent entry (#24869).
  • New features include pausing the whole BitTorrent session, banning IP ranges, multiple email recipients, RSS rule export/import and downloading completed files from the WebUI.

Verdict

Upgrade now if your WebUI is reachable from outside your own network, or if you use email notifications. Otherwise upgrade at your convenience. Back up the config folder first. If you use scripts against the WebAPI, check for the GET-to-POST changes above.

sources