Live › vulnerability › CVE-2026-62965
SABnzbd, a Usenet download tool, passes a user-supplied path to recursive deletion without confining it to the download directory, so an absolute path escapes the intended folder. An attacker holding a valid API key can delete files and directories the SABnzbd process can write to, including its config, queue and downloads.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 21:25 UTC. All times on this page are UTC.
Any SABnzbd instance before 5.1.0Beta3 whose API can be reached by someone holding a valid API key. Exposure depends on whether the web API is exposed beyond trusted users; instances not reachable by untrusted parties carry less risk.
No product ranges from the sources yet.
sabnzbd --version or the version shown in the web interface; versions before 5.1.0Beta3 are affected.5.1.0Beta3 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
SABnzbd is an open source automated Usenet download tool. Prior to 5.1.0Beta3, orphan-job management in sabnzbd/api.py accepts the user-controlled value parameter without path confinement before os.path.join() with download_dir. An absolute path discards that base directory. An attacker with a valid API key can invoke mode=status with name=delete_orphan to reach _api_delete_orphan and remove_all() in sabnzbd/filesystem.py, which uses shutil.rmtree() for recursive deletion. The advisory also identifies _api_add_orphan and _api_delete_all_orphan as affected by the path-validation issue, while its concrete arbitrary-deletion trace is through _api_delete_orphan. The API key is stored in plaintext in sabnzbd.ini. The attacker can delete files or directories writable by the SABnzbd process, including configuration, queue data, and downloads, but system files outside the regular user's ownership are not affected. This issue is fixed in version 5.1.0Beta3.
This page as .md · .json · in your agent: get_signal("CVE-2026-62965")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.