# CVE-2026-121546: ruTorrent before 5.3.20 Path Traversal via datadir Plugin Symlink Following


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-rh8c-6348-v25w

## What is CVE-2026-121546?

CVE-2026-121546 is a medium-severity vulnerability in Novik ruTorrent, published on 3 Nov 2026. 

### Official description

ruTorrent before 5.3.20 contains a path traversal vulnerability in the datadir plugin that allows authenticated users to escape the topDirectory jail because correctDirectory() does not resolve symbolic links. Attackers can submit a datadir path through a symlink under their top directory to create directories and move torrent data to locations writable by the web server or rtorrent.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-121546 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121546 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121546 is a medium-severity vulnerability in Novik ruTorrent, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121546 in the wild and no public exploit code.

Affected product: Novik ruTorrent. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-121546/ (Markdown: https://insights.sbomify.com/CVE-2026-121546/index.md)
```

## Sources

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

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