Skip to content
Fencer Intel
low 2.3

CVE-2026-133238 json

SABnzbd before 5.2.0 Path Traversal via NZB Propername and Episodename Metadata

published 8d ago modified yesterday also EUVD-2026-130318 , GHSA-727m-c877-c8gf

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository sabnzbd/sabnzbd. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
2.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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.

Patch / fix

  • sabnzbd sabnzbd 5.2.0

Is CVE-2026-133238 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2d ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 4.0 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
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected products

  • sabnzbd sabnzbd

Classification

Weakness
  • CWE-23 Relative Path Traversal

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of sabnzbd/sabnzbd published their own advisory on GitHub. Reviewed sources take precedence over it.