# CVE-2025-58763: Tautulli vulnerable to Authenticated Remote Code Execution via Command Injection

> Administrators can achieve remote code execution via command injection in the git update mechanism when Tautulli is manually installed from GitHub.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-jrm9-r57q-6cvf

## What is CVE-2025-58763?

CVE-2025-58763 is a high-severity command injection vulnerability in Tautulli, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. A command injection vulnerability in Tautulli v2.15.3 and prior allows attackers with administrative privileges to obtain remote code execution on the application server. This vulnerability requires the application to have been cloned from GitHub and installed manually. When Tautulli is cloned directly from GitHub and installed manually, the application manages updates and versioning through calls to the `git` command. In the code, this is performed through the `runGit` function in `versioncheck.py`. Since `shell=True` is passed to `subproces.Popen`, this call is vulnerable to subject to command injection, as shell characters within arguments will be passed to the underlying shell. A concrete location where this can be triggered is in the `checkout_git_branch` endpoint. This endpoint stores a user-supplied remote and branch name into the `GIT_REMOTE` and `GIT_BRANCH` configuration keys without sanitization. Downstream, these keys are then fetched and passed directly into `runGit` using a format string. Hence, code execution can be obtained by using `$()` interpolation in a command. Version 2.16.0 contains a fix for the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Tautulli Tautulli.

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

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

## Is CVE-2025-58763 being exploited?

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

## 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-58761](https://insights.sbomify.com/CVE-2025-58761/): Tautulli vulnerable to Unauthenticated Path Traversal in `real_pms_image_proxy` (high 8.6)
- [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-58763 and fix it if it is affected.

What it is: CVE-2025-58763 is a high-severity command injection vulnerability in Tautulli, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58763 in the wild and no public exploit code.

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

## Sources

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

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