SABnzbd path traversal in NZB sorter via metadata
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
SABnzbd has a path traversal flaw in its Sorter that lets an attacker move downloaded files into directories outside the Complete folder, including any directory SABnzbd can write to. An attacker can trigger it remotely, without logging in, by supplying a malicious NZB file with crafted proper name, episode name, or job name values, but a user has to take action to process that file.
Written by a model
Original description
SABnzbd through 5.1.3 contains a path traversal vulnerability in the Sorter that allows attackers to write files outside the Complete folder via crafted propername, episodename or job name (%dn) values. Attackers can supply a malicious NZB with '...' sequences that collapse to '..' after single-pass replacement, moving downloaded files into arbitrary directories writable by SABnzbd.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133238 (SABnzbd through 5.1.3 Path Traversal via NZB Propername and Episodename Metadata), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133238 (entry last updated 2026-11-19):
Affected:
- sabnzbd sabnzbd: through 5.1.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133238 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133238 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sabnzbd/sabnzbd/security/advisories/GHSA-727m-c877-c8gf
- https://github.com/sabnzbd/sabnzbd/pull/3688
- https://github.com/sabnzbd/sabnzbd/commit/c90ab4ee593220d58b9e849269fac846517b13bc
- https://github.com/sabnzbd/sabnzbd/blob/5.1.3/sabnzbd/sorting.py#L400-L402
- https://github.com/sabnzbd/sabnzbd/blob/5.1.3/sabnzbd/filesystem.py#L325-L348
- https://github.com/sabnzbd/sabnzbd
- https://www.vulncheck.com/advisories/sabnzbd-through-5.1.3-path-traversal-via-nzb-propername-and-episodename-metadata
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133238
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133238"}.Affected versions
- sabnzbd sabnzbdthrough 5.1.3
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · sabnzbd/sabnzbd · Advisory GHSA-727m-c877-c8gf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133238 |
| Record | NVD · CVE-2026-133238 |
| Other links 6 | |
| Patch | GitHub · sabnzbd/sabnzbd · Pull request #3688 |
| Patch | GitHub · sabnzbd/sabnzbd · Commit c90ab4ee |
| Repository | GitHub · sabnzbd/sabnzbd · sabnzbd/sorting.py · L400-L402 |
| Repository | GitHub · sabnzbd/sabnzbd · sabnzbd/filesystem.py · L325-L348 |
| Repository | GitHub · sabnzbd/sabnzbd · Repository |
| Link | vulncheck.com · advisories/sabnzbd-through-5.1.3-path-traversal-via-nzb-propername-and-episodename-metadata |
Questions about CVE-2026-133238
Is CVE-2026-133238 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133238?
sabnzbd: through 5.1.3.
Source: cve.now feed data
Related
- CVE-2023-34237Remote code execution via specially crafted script settings in SABnzbd
- CVE-2026-62965SABnzbd: Orphan-job path traversal permits arbitrary file deletion
- CVE-2021-29488Creation of files outside the Download Folder through malicious PAR2 files
- CVE-2026-132233In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection
- CVE-2026-120495Arbitrary file write and code execution via crafted Synthetic Monitoring agent data
- CVE-2026-133080In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings
No corrections so far. Something wrong on this page? Report an error.