# CVE-2025-58761: Tautulli vulnerable to Unauthenticated Path Traversal in `real_pms_image_proxy` > Unauthenticated attackers can read arbitrary files via path traversal, potentially stealing credentials to gain administrative control over Tautulli. - **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-r732-m675-wj7w ## What is CVE-2025-58761? CVE-2025-58761 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 `real_pms_image_proxy` endpoint in Tautulli v2.15.3 and prior is vulnerable to path traversal, allowing unauthenticated attackers to read arbitrary files from the application server's filesystem. The `real_pms_image_proxy` is used to fetch an image directly from the backing Plex Media Server. The image to be fetched is specified through an `img` URL parameter, which can either be a URL or a file path. There is some validation ensuring that `img` begins with the prefix `interfaces/default/images` in order to be served from the local filesystem. However this can be bypassed by passing an `img` parameter which begins with a valid prefix, and then adjoining path traversal characters in order to reach files outside of intended directories. An attacker can exfiltrate files on 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-27 (Path Traversal: 'dir/../../filename') ## Which versions are affected by CVE-2025-58761? It affects 1 product. Products: Tautulli Tautulli. ## How do I fix CVE-2025-58761? No fix has been published for CVE-2025-58761 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-58761 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58761 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-58760](https://insights.sbomify.com/CVE-2025-58760/): Tautulli vulnerable to Unauthenticated Path Traversal in `/image` endpoint (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-58761 and fix it if it is affected. What it is: CVE-2025-58761 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-58761 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-58761/ (Markdown: https://insights.sbomify.com/CVE-2025-58761/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58761 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58761 - OSV: https://osv.dev/vulnerability/CVE-2025-58761 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-58761/ Summaries are generated and may contain mistakes; the official description above is the record.