SABnzbd: Orphan-job path traversal permits arbitrary file deletion
Impact
SABnzbd versions prior to 5.1.0Beta3 have a path traversal weakness, allowing an attacker with a valid API key to delete arbitrary files or directories writable by the SABnzbd process. The issue is due to improper path confinement in orphan-job management. An attacker can exploit this to delete configuration, queue data, and downloads.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
sabnzbd · GitHub_M
sabnzbd
1 range
sabnzbd · GitHub_M
sabnzbd
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 5.1.0Beta3
Other versions: unknown
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-62965View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.