# CVE-2026-133238: SABnzbd before 5.2.0 Path Traversal via NZB Propername and Episodename Metadata


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 20 Nov 2026
- **Also known as:** GHSA-727m-c877-c8gf, GHSA-82w5-pjfh-hq29

## What is CVE-2026-133238?

CVE-2026-133238 is a low-severity vulnerability in sabnzbd, published on 19 Nov 2026. 

### Official description

SABnzbd before 5.2.0 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.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-133238?

1 open source package ship an affected version, including sabnzbd/sabnzbd.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `sabnzbd/sabnzbd` | GitHub | `pkg:github/sabnzbd/sabnzbd` | All versions | 5.2.0 |

## How do I fix CVE-2026-133238?

Upgrade sabnzbd/sabnzbd to 5.2.0 or later.

## Is CVE-2026-133238 being exploited?

There is no known exploitation of CVE-2026-133238 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133238 and fix it if it is affected.

What it is: CVE-2026-133238 is a low-severity vulnerability in sabnzbd, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133238 in the wild and no public exploit code.

Affected packages and fixed versions:
- sabnzbd/sabnzbd (GitHub): affected all versions; fixed in 5.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133238/ (Markdown: https://insights.sbomify.com/CVE-2026-133238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133238
- OSV: https://osv.dev/vulnerability/CVE-2026-133238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133238/
Summaries are generated and may contain mistakes; the official description above is the record.
