# CVE-2026-40605: Tautulli Vulnerable to Authenticated Path Traversal in Cache Deletion API

> Authenticated attackers can exploit a path traversal flaw in the cache deletion API to delete arbitrary directories, causing data loss and service disruption.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-fg46-xx7h-mhwr

## What is CVE-2026-40605?

CVE-2026-40605 is a medium-severity path traversal vulnerability in Tautulli, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.1, a path traversal vulnerability in the cache deletion endpoint allows authenticated API access to delete directories outside the configured cache path. This can cause arbitrary data loss and service disruption. Version 2.17.1 fixes the issue.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-40605 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40605 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40605 is a medium-severity path traversal vulnerability in Tautulli, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40605 exists.

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

## Sources

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

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