# CVE-2025-58760: Tautulli vulnerable to Unauthenticated Path Traversal in `/image` endpoint

> Unauthenticated attackers can read arbitrary files, including credentials and tokens, potentially leading to administrative control of the Tautulli application.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-8g4r-8f3f-hghp

## What is CVE-2025-58760?

CVE-2025-58760 is a high-severity path traversal vulnerability in Tautulli, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. The `/image` API endpoint in Tautulli v2.15.3 and earlier is vulnerable to path traversal, allowing unauthenticated attackers to read arbitrary files from the application server's filesystem. In Tautulli, the `/image` API endpoint is used to serve static images from the application's data directory to users. This endpoint can be accessed without authentication, and its intended purpose is for server background images and icons within the user interface. Attackers can exfiltrate files from the application file system, including the `tautulli.db` SQLite database containing active JWT tokens, as well as the `config.ini` file which contains the hashed admin password, the JWT token secret, and the Plex Media Server token and connection details. If the password is cracked, or if a valid JWT token is present in the database, an unauthenticated attacker can escalate their privileges to obtain administrative control over the application. Version 2.16.0 contains a fix for the issue.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-58760?

It affects 1 product.


Products: Tautulli Tautulli.

## How do I fix CVE-2025-58760?

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

## Is CVE-2025-58760 being exploited?

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

## Other vulnerabilities in Tautulli

- [CVE-2025-58762](https://insights.sbomify.com/CVE-2025-58762/): Tautulli vulnerable to Authenticated Remote Code Execution via write primitive and `Script` notification agent (critical 9.1)
- [CVE-2026-31831](https://insights.sbomify.com/CVE-2026-31831/): Tautulli: Unauthenticated Path Traversal in `/newsletter/image/images` endpoint (high 8.7)
- [CVE-2025-58761](https://insights.sbomify.com/CVE-2025-58761/): Tautulli vulnerable to Unauthenticated Path Traversal in `real_pms_image_proxy` (high 8.6)
- [CVE-2025-58763](https://insights.sbomify.com/CVE-2025-58763/): Tautulli vulnerable to Authenticated Remote Code Execution via Command Injection (high 8.1)
- [CVE-2026-28505](https://insights.sbomify.com/CVE-2026-28505/): Tautulli: RCE via eval() sandbox bypass using lambda nested scope to escape co_names whitelist check (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58760 and fix it if it is affected.

What it is: CVE-2025-58760 is a high-severity path traversal vulnerability in Tautulli, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58760 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-2025-58760/ (Markdown: https://insights.sbomify.com/CVE-2025-58760/index.md)
```

## Sources

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

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