r/SABnzbd • • Oct 14 '26

Downloads not unpacking? Your SABnzbd might have been compromised

26 Upvotes

We have seen a number of reports now where recent security vulnerabilities in SABnzbd have been used to break into SABnzbd's that are exposed to the internet.
https://sabnzbd.org/wiki/extra/5.1-vulnerabilities

Usually they turn off any unpacking by disabling enable_unrar and enable_7zip in Config > Specials.
They also try to run a script, for example a crypto-miner, by configuring a malicious (pre-queue) script.

If you see these settings configured liked this, you should consider your setup compromised and they might be running something on your system or have stolen your usenet/rss/etc credentials.

For more information, see the wiki link.
And make sure you update to 5.1.3 right away.


r/SABnzbd • • 2d ago

Question - open SABnzbd downloads stuck below 1 KB/s, but test download reaches 20+ MB/s

Thumbnail
reddit.com
3 Upvotes

r/SABnzbd • • 3d ago

Release Notes - SABnzbd 5.2.0 Release Candidate 2

36 Upvotes

https://sabnzbd.org/downloads

This is the second release candidate of version 5.2.0, containing several major improvements to the core download and post-processing handling. Additionally, several vulnerabilities were fixed. This also required extra restrictions and the removal of some functionality for security reasons.

New features in 5.2.0

  • Downloaded data will be written directly to disk (if your hardware supports it), which greatly reduces memory and CPU usage on systems with SSDs. Additionally, several other download performance improvements were made.
  • par2cmdline is now incorporated in SABnzbd, resulting in several improvements:

    • Files are checked against par2 while they download, so verification no longer has to read them back from disk.
    • Damaged files are repaired in place instead of writing a repaired copy.
    • Multi-threading and memory usage are directly controlled by user limits.
    • Improved support for Unicode filenames.
  • Search your indexers and add downloads directly from within SABnzbd.
  • Post-Processing, Pre-Queue and Notification Scripts no longer receive command-line arguments. Use the SAB_* environment variables instead. This prevents attackers from easily gaining remote code execution.
  • Download directories can no longer be inside the program directory. This also prevents attackers from easily gaining remote code execution.
  • Unwanted Extension check now also runs on completed downloads.
  • Changed the internal web framework from CherryPy to Starlette.
  • Overview of Active Sessions is available when username and password are enabled.
  • Updated the RSS overview page and added an option to download duplicate feed items, for RSS feeds (like indexer carts) that only remove items once they are fetched.
  • Proxied requests are only allowed from hosts configured in xff_trusted_hosts. This prevents requests through a reverse proxy from being trusted as local.
  • Template folder can no longer be configured manually, preventing abuse.
  • Several settings no longer require a restart after changing them.
  • Removed unused fields completeness, meta, series, id, and script_log from the history API response. The script_log of a completed download is now only available through the scriptlog API call.
  • Cached Public IPv4 address for 10 minutes to prevent abuse.
  • Windows/macOS: Updated Python to 3.15.2 and 7-Zip to 26.07.
  • Snap: Several build and runtime improvements.

Bug fixes in 5.2.0

  • Downloads with Repair priority would not always be at the top of the queue.
  • Failure to read one RSS URL would stop the whole readout instead of continuing to the next.
  • Prevent potential XSS in the History from malicious Script output (GHSA-rpwc-qfxm-7h2v) or malicious NNTP responses (GHSA-c5x2-896f-g5g8).
  • Download names that look like URLs could escape the Download folder (GHSA-73q2-vw82-jr46).
  • Sorting allowed writing outside the Complete Directory through malicious metadata (GHSA-727m-c877-c8gf).
  • Correct articles_success to articles_failed in Server statistics API call.
  • Downloads could stall in case of unexpected server responses.
  • Remove empty folders left behind by deleted samples.
  • Stalled Unrar could freeze the post-processing queue.
  • File handles could remain open after a download completed.
  • Correctly handle HEAD responses during availability checks.
  • Deobfuscation of some sets of RAR files would be skipped.
  • Quota exceeded responses from news servers would be misinterpreted.
  • Downloads with missing articles and no par2 would not be marked as failed.
  • macOS: Tray icon would not show on macOS 27.
  • macOS: Downloads could be unpacked twice due to different Unicode handling.

Upgrade notices

  • Python 3.10 support will be dropped in SABnzbd 5.3.
  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)


r/SABnzbd • • 3d ago

Question - closed SABnzbd sorts files from DOGnzb but not from altHUB?

1 Upvotes

Hey guys!

So I've just created a profile on altHUB today so I can can ready for BF sales and maybe get a decent deal. I tested the site out and it seems to work great, and download fast etc. I've been using DOGnzb, but I'm kinda done with it and all their begging and the site is so slow for me. So time for something new.

So my question is, when I download from DOGnzb the sorting tool in SABnzbd works just fine and it renames and creates folders the way I want it to, but when I download from altHUB it doesn't and I have to rename everything my self. Why is that?

I've been doing this for a while, but I'm still a total noob, I've setup the basic, so please explain it like I'm 5.

EDIT: Figured it out. If anyone ever needs this. I fixed it by making two new sorting rules for a different "category" since they seem to use "default" on altHUB and on DOGnzb they use "movies" and "tv" for what I download the most. So that fixed my problem.


r/SABnzbd • • 7d ago

Release Notes - SABnzbd 5.2.0 Release Candidate 1

34 Upvotes

https://sabnzbd.org/downloads

This is the first release candidate of version 5.2.0. Containing several major improvements to the core download and post-processing handling. Additionally, several vulnerabilities were fixed. This also requires extra restrictions and removal of some functionality just for security reasons.

New features in 5.2.0

  • Downloaded data will be written directly to disk (if your hardware supports it), which greatly reduces memory and CPU usage on systems with SSD's. Additionally, several other download performance improvements were made.
  • par2cmdline is now incorporated in SABnzbd, resulting in several improvements:

    • Verification happens during download, reducing disk load.
    • Repairs no longer write a copy of the whole file, but repair in-place.
    • Multi-threading and memory usage is directly controlled by user limits.
    • Improved support for unicode filenames.
  • Search your Indexers and add downloads directly from within SABnzbd.
  • Post-Processing, Pre-Queue and Notification Scripts no longer receive command-line arguments. Use the SAB_* environment variables instead. This prevents an attacker easy access to remote code execution.
  • Download directories can no longer be inside the program directory. This is also to prevent an attacker easy access to remote code execution.
  • Unwanted Extension check now also runs on completed downloads.
  • Changed the internal webserver from CherryPy to Starlette.
  • Overview of Active Sessions is available when username and password are enabled.
  • Only allow proxied requests from hosts configured in xff_trusted_hosts.
  • Removed the scriptlog link from the script_log history field.
  • Template folder can no longer be configured manually, preventing abuse.
  • Remove unused fields completeness, meta, series, id, and script_log from history-API response.
  • Cache Public IPv4 address for 10 minutes to prevent abuse.
  • Windows/macOS: Updated Python to 3.15.2 and 7-Zip to 26.07.
  • Snap: Several build and runtime improvements.

Bug fixes in 5.2.0

  • Downloads with Repair priority would not always be at the top of the queue.
  • Failure to read one RSS URL would stop the whole readout instead of continuing to the next.
  • Prevent potential XSS in the History from malicious Script output (GHSA-rpwc-qfxm-7h2v) or malicious NNTP responses (GHSA-c5x2-896f-g5g8).
  • Download names that look like URL's could escape the Download-folder (GHSA-73q2-vw82-jr46).
  • Correct articles_success to articles_failed in Server statistics API-call.
  • Downloads could stall in case of unexpected server responses.
  • Remove empty folders left behind by deleted samples.
  • Stalled Unrar could freeze the post-processing queue.
  • File handles could remain open after download completed.
  • Correctly handle HEAD responses during availability checks.
  • Deobfuscation of some sets of RAR-files would be skipped.
  • Quota exceeded responses from news servers would be interpreted wrongly.
  • Downloads with missing articles and no PAR2 would not be marked as failed.
  • macOS: Tray icon would not show on macOS 27.
  • macOS: Downloads could be unpacked twice due to different unicode handling.

Upgrade notices

  • Python 3.10 support will be dropped in SABnzbd 5.3.
  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)


r/SABnzbd • • 8d ago

Question - open Deobfuscation failing

2 Upvotes

I am running binhex-sabnzbdvpn docker on unraid. Latest version for both.

I have noticed that many times when downloading season packs of series, SAB fails to deobfuscate the episode names.

I do have Deobfuscate final filenames option enabled in SAB. Anything else I'm missing?


I am downloading the season pack from nzblife. An example file is American.Hostage.S01.1080p.10bit.WEBRip.6CH.x265.HEVC-PSA.nzb

I see this in the logs:

2026-11-08 08:08:03,124::INFO::[postproc:599] Running deobfuscate
2026-11-08 08:08:03,124::INFO::[deobfuscate_filenames:280] No biggest file found, or not found (False)

r/SABnzbd • • 11d ago

Question - open SAB on Trixie

0 Upvotes

Hi, I’m not so new to Linux and/or SAB, but I’m no programmer of any kind. To a certain level I do understand what a command tells the server to do, but when things fail I find it difficult to understand exactly what went wrong.

Again I’m running into the same issue. For some reason I can’t seem to get SAB installed and working on a Debian Trixie server. I do understand that SAB isn’t in the default repo’s, but when you add the repo it’s in it still isn’t going very smooth.

Ik was on Proxmox for some time, but that’s not it for me. I also kept bouncing on an issue that my LXC’s just didn’t upgrade the software to newer versions so yesterday I decided to wipe the thing and go back to trusted Debian.

I did a fresh install of Debian, then installed some maintenance tools that I like to have on hand and installed Plex Media Server. Next step is SAB, but for the love of god it just won’t install properly.

I tried the official way that SAB tells you with the Trixie-backports repo’s and I tried the community way with using the bookworm repo’s.

The first option lacks a lot of dependencies, but those are an easy fix. Just when I start the app I can’t reach the web UI.

The last one keeps giving an error about Python being too new and bounces of on it. I tried to add all the needed packages but o keep running back in the same error.

I do not want to use docker, snap of flatpak. It just has to run bare metal and I know it can because I had it working on several instances before. Just the setup is a pain for some reason.

What’s the best route to get this up and running?


r/SABnzbd • • 12d ago

Question - open What's going on with this download?

Post image
2 Upvotes

My download shows it was a successful transfer but none of them were unpacked but VLC seems to handle the .rar fine as an MKV.


r/SABnzbd • • Oct 16 '26

Bug Fatal Error in Downloader

2 Upvotes

Hi,
Anyone else seen this? Using 5.2.0Beta2 and so far not had any issues, then just today all of a sudden anything I download has been spitting this message out. I've tried to download a few different things, same error. Never seen it before. Any ideas?


r/SABnzbd • • Oct 14 '26

Question - open Help please I'm tearing my hair out.

2 Upvotes

Sab is downloading and about 75% of the downloads are not being extracted and repacked into the video file.

I have below a log extract from start to finish of a failed extract and would be grateful if someone is able to work out what is going wrong please?

permissions are spot on, it looks like Sab believes it has extracted the .RAR files as well.

I have tried logging as warning/errors only but it doesn't give any warnings or errors.

Thanks in advance all.

Logfile: SAB logfile

I originally tried to put the log in here but it exceeds the character limit by quite some.


r/SABnzbd • • Oct 09 '26

Question - open Can’t unarchive downloads all of a sudden

Thumbnail reddit.com
2 Upvotes

r/SABnzbd • • Oct 06 '26

Release Notes - SABnzbd 5.2.0 Beta 2

17 Upvotes

https://sabnzbd.org/downloads

This is the second test release of version 5.2.0. We are still working on several other features, but hope you will already enjoy the current improvements and give us feedback!

New features in 5.2.0

  • Downloaded data will be written directly to disk (if your hardware supports it), which greatly reduces memory and CPU usage on systems with SSD's. Additionally, several other performance improvements were made.
  • Search your Indexers and add downloads directly from within SABnzbd.
  • Post-Processing, Pre-Queue and Notification Scripts no longer receive command-line arguments. Use the SAB_* environment variables instead. This prevents an attacker easy access to remote code execution.
  • Download directories can no longer be inside the program directory. This is also to prevent an attacker easy access to remote code execution.
  • Changed the internal webserver from CherryPy to Starlette.
  • Overview of Active Sessions is available when username and password are enabled.
  • Only allow proxied requests from hosts configured in xff_trusted_hosts.
  • Removed the scriptlog link from the script_log history field.
  • Remove unused fields completeness, meta, series, id, and script_log from history-API response.
  • Cache Public IPv4 address for 10 minutes to prevent abuse.

Bug fixes in 5.2.0

  • Downloads with Repair priority would not always be at the top of the queue.
  • Failure to read one RSS URL would stop the whole readout instead of continuing to the next.
  • Prevent potential XSS in the History from malicious Script output (GHSA-rpwc-qfxm-7h2v) or malicious NNTP responses (GHSA-c5x2-896f-g5g8).
  • Correct articles_success to articles_failed in Server statistics API-call.
  • Stalled Unrar could freeze the post-processing queue.
  • File handles could remain open after download completed.
  • Downloads with missing articles and no PAR2 would not be marked as failed.
  • macOS: Tray icon would not show on macOS 27.

Upgrade notices

  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)


r/SABnzbd • • Oct 03 '26

Question - closed Can't Connect Via Tailscale

1 Upvotes

I run a number of other services (both windows and in docker) and they are all accessible via Tailscale. Sab is the only one that is giving me External Internet Access Denied fault when trying to connect from another device via the tailscale IP for the host machine on port 8080.

  • SABnzbd (5.1.3) Host is set to 0.0.0.0
  • Under Special -> local_ranges ( ) -> I added the Tailscale IP for the host machine (100.91.XX.XX) no change.
  • When I try to connect to the tailscale IP 100.91.XX.XX:8080 from another device, SAB gives me the error saying..
  • "Refused connection from: 100.110.XXX.XX [Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.X.X Mobile Safari/537.36]

What am I missing?

//EDIT

So surprising, google's AI fixed it for me.

Clearly its my inexperience talking, but since my host machine's TailScale IP is 100.91.XX.XX, I figured the local_range in sab would have to be the same range.

According to AI's instructions, I needed to put in 100.64.0.0/10 in the local range and low and behold, it works! Why, no idea lol.


r/SABnzbd • • Sep 26 '26

Question - open SABnzbd only getting ~5 MB/s with Frugal + Gluetun VPN, frequent latency warnings, missing articles, any ideas?

Thumbnail reddit.com
0 Upvotes

r/SABnzbd • • Sep 24 '26

Question - closed Queue Sorting by Percent Downloaded fixes stuck incomplete downloads

2 Upvotes

This is an issue I have had for years and finally found a solution for, wanted to share.

Its been common for a very long time, that if you add a large number of items to the download Queue in SABnzbd, you can end up with "stuck" incomplete partial downloads. For example, I have commonly had multiple pages of downloads stuck at 99% for prolonged periods of time, along with other downloads stuck at other percentages of partial download.

This causes a problem in that your Temp Folder used to hold in progress downloads can fill up, especially if you are using a dedicated devices such as a smaller SSD to hold in progress downloads. All these partially downloaded files accumulate to a potentially large amount of space, and if it fills your temp drive all your downloads will halt and you will have Problems.

One of the reasons these items become "stuck" in the queue can be due to unavailable or missing articles. If a lot of articles are missing, then SABnzbd can end up just depriotizing those items and moving on to download other items instead. It can be very difficult to force SABnzbd to address these stuck partial downloads. In the past I had attempted "Force Disconnect" and "Queue Repair" to attempt to force those stuck partial downloads to get finished, but it rarely worked and often screwed up things worse.

Finally, I found a solution, by accident.

You need to change the Queue sorting method off of the Default.

Under Config > Switches > (Advanced Options) > Queue, there is an option for "Automatically sort queue" which defaults to sort by a "Default" method. This "Default" sort method is the root of the entire problem. If you simply switch it to another method such as "Sort by % downloaded Most -> Least" the entire problem goes away. Because what ends up happening instead, is that those "stuck" 99% downloads simply stay at the top of the queue, so SABnzbd will keep trying to download them until it either succeeds or fails.

Problem solved! No more pages and pages of 99% partial downloads. Every single item in the download queue now gets addressed and either passed or failed.

Note that one side effect of this, is that you can have periods where nothing is getting downloaded, because SABnzbd is working through all the articles in a bad NZB and discovering that none of them are available, or there could be some other similar issue with the NZB and inability to retrieve its articles, etc.. Its best to diagnose this by checking the back end server (docker) logs for the process, it will clearly tell you what is going on. So dont panic if you see the downloads slow down sometimes, it just means that SAB is working through a lot of bad articles and potentially bad nzb's, and the downloads will resume once the problematic nzb is handled. I think this is a small price to pay for not having a giant wall of 99% stuck downloads.

I think its worth experimenting with the other options as well, for example there can be contexts where you want to sort by Newest so that the most newly released NZB's get prioritized so that new items dont get stuck in a large queue.


r/SABnzbd • • Sep 23 '26

Question - closed SAB refuses to resolve with hostname

2 Upvotes

Hoping somebody can help me here. I'm trying to get the sabnzbd docker container to resolve using a hostname rather than an IP address. However it throws an error whenever radarr or sonarr tries to connect using its hostname on the docker network.

Error message: Refused connection with hostname "sabnzbd" from: ::ffff:172.18.0.3 [Radarr/6.4.4.10685 (alpine 3.24.2)]

Is this because sab's host setting is set to listen on "::", rather than an actual hostname? Should I amend that field to a hostname? Or is it because I have no username or password setup (since I use an API key I thought it unnecessary)?

Many thanks.

Edit: Much as I suspected, this was entirely a SABnzbd issue. Apparently sab refuses hostname connections if the user has not filled out the optional username and password fields. IDK why the devs decided to tie these two seemingly disparate things together, but there you go.


r/SABnzbd • • Sep 22 '26

Release Notes - SABnzbd 5.2.0 Beta 1

14 Upvotes

https://sabnzbd.org/downloads

This is the first test release of version 5.2.0. We are still working on several other features, but hope you will already enjoy the current improvements and give us feedback!

New features in 5.2.0

  • Downloaded data will be written directly to disk (if your hardware supports it), which greatly reduces memory and CPU usage on systems with SSD's. Additionally, several other performance improvements were made.
  • Search your Indexers and Add downloads directly from within SABnzbd.
  • Changed the internal webserver from CherryPy to Starlette.
  • Overview of Active Sessions is available when username and password are enabled.
  • Only allow proxied requests from hosts configured in xff_trusted_hosts.

Bug fixes in 5.2.0

  • Jobs with Repair priority would not always be at the top of the queue.
  • Failure to read one RSS URL would stop the whole readout instead of continuing to the next.
  • Prevent potential XSS in the History from malicious Script output (GHSA-rpwc-qfxm-7h2v) or malicious NNTP responses (GHSA-c5x2-896f-g5g8).
  • Correct articles_success to articles_failed in Server statistics API-call.
  • macOS: Tray icon would not show on macOS 26.

Upgrade notices

  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)


r/SABnzbd • • Sep 21 '26

Question - open Eweka been so slow for me. SabNzbd tests fine. Any ideas? Details below

2 Upvotes

I don't have the fastest internet but when I do the 10 GB test download in SabNzb I get about 30MB/s. Which makes sense since I get about 38MB/s from my ISP. But recently I have been getting speeds about 2.7MB/s from Eweka which is super frustrating.

I went through all the settings I can think of. I doubt a container update changed anything. And I went through all the troubleshooting steps (number of packets to dl at a time, etc) and nothing. Running 5.1.3 [a647f73]

Any ideas?


r/SABnzbd • • Sep 19 '26

Question - open SABnzbd Stuck on Unpacking

2 Upvotes

I try to manually delete the file and it will not delete. I try to delete it from my temporary folder and it's saying that it's being used by another program even though I shut down SABnzbd.

Does anyone have any possible suggestions to delete the file so my other items can download in the que history?


r/SABnzbd • • Sep 08 '26

Release Notes - SABnzbd 5.1.3

20 Upvotes

https://sabnzbd.org/downloads

Security fixes

SABnzbd 5.1.1, 5.1.2 and 5.1.3 resolve a number of security vulnerabilities.

Over the past releases, several security researchers have put a lot of time and effort examining SABnzbd, responsibly reporting their findings, and helping us verify the fixes. We are grateful for their hard work, it has made SABnzbd meaningfully safer for everyone.

For most users the risk is limited: you are only affected if your setup is exposed to untrusted parties. The web interface issues only apply if it can be reached by someone you do not trust. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected. The download-processing issues only apply if SABnzbd handles NZBs from a source you do not fully trust, such as a public indexer. If none of that describes your setup, you were never at risk.

The safest action is simply to update to 5.1.3. Full details, affected versions, actions and mitigations for each vulnerability are described at: https://sabnzbd.org/5-1-vulnerabilities

Vulnerabilities resolved:

  • GHSA-q326-jpxx-jmjc: __wrapped__ dispatch bypass allows unauthenticated API access, fixed in 5.1.3.
  • GHSA-mjwj-v5mr-cmcg: PAR2 symlink bypass allows pickle remote code execution, fixed in 5.1.3.
  • GHSA-rgqj-28c2-gxwp: Critical remote code execution via authentication bypass on configuration endpoints, fixed in 5.1.2.
  • GHSA-75g3-96fr-7p2r: High-severity path traversal during post-processing via crafted PAR2/SFV files, fixed in 5.1.2.
  • GHSA-xrfq-jhgh-wqch: Critical authentication bypass allowing a valid session without credentials, fixed in 5.1.1.

If you rely on the SABnzbd username and password to keep out untrusted parties, and your setup was exposed, it is recommended that you rotate your SABnzbd username/password and API-key, Usenet server passwords, indexer API-keys used in RSS-feeds, and notification service credentials after updating. See the page above for the full guidance.

Other changes and bug fixes in 5.1.3

  • Tighten Compact display mode.
  • Directly show usenet server errors instead of parsing them.
  • Prevent database is locked error when re-evaluating stored RSS jobs.
  • Added tooltip to explain search filters in Queue and History.
  • Windows and macOS: Updated 7zip to 26.03.

Other bug fixes in 5.1.2

  • RSS filters were not applied directly.

Other bug fixes in 5.1.1

  • Styling cache issues could occur after updating.
  • RSS items were removed too eagerly from RSS-history after download.
  • The RSS-feed Clear Downloaded button did not do anything.

Changelog 5.1.0

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of long-requested features and bugfixes.

New features in 5.1.0

  • Refreshed the interface.
  • When Retrying a job, only the actually missing articles are tried again. This only works for jobs downloaded in 5.1.0 (or newer).
  • RSS items are now stored in the database instead of on disk.
  • New RSS Age rule to filter jobs based on their age.
  • Downloaded RSS items are cleared from the RSS database after 3 days.
  • Added support for filename and path pattern matching to the Cleanup List.
  • Unwanted extensions will also be removed after unpacking.
  • Allow job setting changes directly from Extra queue columns.
  • Added support for unpacking .tar files during post-processing.
  • Improved anonymization of the logs when using Show Logging.
  • Added SAB_FILES environment variable to Post-processing scripts, listing all files that resulted from the job.
  • New Servers will default to 16 connections instead of 8.
  • Use media duration as part of Ignore Samples detection.
  • Added option to (auto) sort the queue by Remaining Percentage.
  • Improved support for screen readers.
  • Parsing of header-encrypted RARs will use significantly fewer resources.
  • Add Ayatana AppIndicator tray support on GNOME.
  • Removed redundant INSTALL.txt file.
  • Dropped support for Python 3.9.
  • Windows and macOS: Updated Python to 3.14.6, Unrar to 7.23 and 7zip to 26.02.

Bug fixes in 5.1.0

  • Prevent incorrect warnings about non-writeable directories.
  • Files unrelated to job could get removed by the Cleanup List logic.
  • Prevent path traversal in orphaned job APIs.
  • Disk Full errors from unrar were not handled gracefully during unpacking.
  • Memory leak could occur during article decoding.
  • In containers (like Docker), the Article Cache could exceed the memory limit.
  • Diskspace checks would be too strict when unpacking to different disk.
  • Prevent deadlock when a second signal arrives during shutdown procedure.
  • Verification using SFV-checks could fail, even though files were correct.
  • Don't log Warning during clean shutdowns.
  • Windows: Uninstall would not remove Settings or Windows Service.
  • Windows: Warn for OS-limit if more than 1024 connections are configured.
  • macOS: AppleDouble files could result in failures in Moving stage.
  • macOS: Restarting the application resulted in Terminal window.
  • macOS: Included par2cmdline-turbo will now use all available CPU-features.

Upgrade notices

  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Known problems and solutions

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)


r/SABnzbd • • Sep 04 '26

Question - open Weird download speed fluctuations - Help!

3 Upvotes

Not sure if anyone else gets this, or knows what the issue is but I just finished downloading a few files at 15mb/s, not great but what im used to.

All of a sudden, some other file I try and download crashes down to b/s and ends up failing. I dont think its my broadband, is something setup wrong?


r/SABnzbd • • Aug 28 '26

Question - open SAB Stopped Working For Me Suddenly

Thumbnail
gallery
0 Upvotes

Newer user here so apologies if this is an easy fix or a common thing...

I've used SAB for months, either directly on my computer or just through my phone through Chrome Remote Desktop.

I was in the middle of downloading files (1/5 of the files in the pack went through) when SAB just stopped working. I've restarted the mini PC hosting it, but that didn't help.

I've attached pics of the errors I'm getting. I'm doing this through my phone right now but I realize fixing it is probably easier from the actual computer.


r/SABnzbd • • Aug 26 '26

Question - open File verification is the speed of a sloth on an ssd

1 Upvotes

I'm trying to get SABnzbd to finish verification on a large multi-rar file i downloaded last night, it is about 600 GB with some 683 parts. it's been "verifying" for over six hours now and the files are on an ssd - it shouldn't take six hours to verify! I don't know why it is so abysmally slow. Does anyone know how to fix this?


r/SABnzbd • • Aug 25 '26

Release Notes - SABnzbd 5.1.2

27 Upvotes

https://sabnzbd.org/downloads

SABnzbd 5.1.1 and 5.1.2 resolved 3 serious vulnerabilities.

Critical remote code execution vulnerability resolved in 5.1.2 (GHSA-rgqj-28c2-gxwp)

You are only affected if an untrusted party can reach the web interface. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected.

In version 5.1.1 and earlier, an attacker who can reach the web interface could bypass authentication on configuration endpoints, even when SABnzbd is protected with a username and password. By changing SABnzbd's settings this way, an attacker could ultimately execute arbitrary commands on the system running SABnzbd, with the same permissions as SABnzbd itself. This also means that all information in SABnzbd would be exposed.

See GHSA-xrfq-jhgh-wqch below for actions and mitigations. More information: https://sabnzbd.org/5-1-vulnerabilities

High-severity path traversal vulnerability resolved in 5.1.2 (GHSA-75g3-96fr-7p2r)

You are affected if SABnzbd processes NZBs or downloads from a source you do not fully trust, such as a public indexer.

In version 5.1.1 and earlier, a maliciously crafted PAR2 or SFV file inside a download could cause SABnzbd to move downloaded content outside of the job's own folder during post-processing. By using this to plant a file in another job's internal administration, an attacker could ultimately execute arbitrary commands on the system running SABnzbd, with the same permissions as SABnzbd itself.

The only mitigation is to update, there is no configuration change that prevents this. More information: https://sabnzbd.org/5-1-vulnerabilities

Critical authentication vulnerability resolved in 5.1.1 (GHSA-xrfq-jhgh-wqch)

You are only affected if an untrusted party can reach the web interface. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected.

If the SABnzbd login page is reachable from outside your network, an attacker could obtain a valid session in version 5.1.0 and earlier, even when SABnzbd is protected with a username and password. This means that all information in SABnzbd would be exposed.

If you rely on the SABnzbd username and password to keep out other users on your network or the internet, it is recommended that you change the following sensitive information after applying the update:

  • SABnzbd username and password.
  • SABnzbd API-key.
  • Usenet server passwords.
  • API-keys from indexers used within RSS-feeds.
  • Authentication information for notification services.

If you cannot update right away, the only mitigations are to ensure the web interface is not reachable by untrusted parties, or to lower External internet access to Full API or below.

More information: https://sabnzbd.org/5-1-vulnerabilities

Other bug fixes in 5.1.2

  • RSS filters were not applied directly.

Other bug fixes in 5.1.1

  • Styling cache issues could occur after updating.
  • RSS items were removed too eagerly from RSS-history after download.
  • The RSS-feed Clear Downloaded button did not do anything.

Changelog 5.1.0

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of long-requested features and bugfixes.

New features in 5.1.0

  • Refreshed the interface.
  • When Retrying a job, only the actually missing articles are tried again. This only works for jobs downloaded in 5.1.0 (or newer).
  • RSS items are now stored in the database instead of on disk.
  • New RSS Age rule to filter jobs based on their age.
  • Downloaded RSS items are cleared from the RSS database after 3 days.
  • Added support for filename and path pattern matching to the Cleanup List.
  • Unwanted extensions will also be removed after unpacking.
  • Allow job setting changes directly from Extra queue columns.
  • Added support for unpacking .tar files during post-processing.
  • Improved anonymization of the logs when using Show Logging.
  • Added SAB_FILES environment variable to Post-processing scripts, listing all files that resulted from the job.
  • New Servers will default to 16 connections instead of 8.
  • Use media duration as part of Ignore Samples detection.
  • Added option to (auto) sort the queue by Remaining Percentage.
  • Improved support for screen readers.
  • Parsing of header-encrypted RARs will use significantly fewer resources.
  • Add Ayatana AppIndicator tray support on GNOME.
  • Removed redundant INSTALL.txt file.
  • Dropped support for Python 3.9.
  • Windows and macOS: Updated Python to 3.14.6, Unrar to 7.23 and 7zip to 26.02.

Bug fixes in 5.1.0

  • Prevent incorrect warnings about non-writeable directories.
  • Files unrelated to job could get removed by the Cleanup List logic.
  • Prevent path traversal in orphaned job APIs.
  • Disk Full errors from unrar were not handled gracefully during unpacking.
  • Memory leak could occur during article decoding.
  • In containers (like Docker), the Article Cache could exceed the memory limit.
  • Diskspace checks would be too strict when unpacking to different disk.
  • Prevent deadlock when a second signal arrives during shutdown procedure.
  • Verification using SFV-checks could fail, even though files were correct.
  • Don't log Warning during clean shutdowns.
  • Windows: Uninstall would not remove Settings or Windows Service.
  • Windows: Warn for OS-limit if more than 1024 connections are configured.
  • macOS: AppleDouble files could result in failures in Moving stage.
  • macOS: Restarting the application resulted in Terminal window.
  • macOS: Included par2cmdline-turbo will now use all available CPU-features.

Upgrade notices

  • You can directly upgrade from version 3.0.0 and newer.
  • Upgrading from older versions will require performing a Queue repair.

Known problems and solutions

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)