High Injection exploit reference

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

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.

Published Sep 9, 2025 · Updated Oct 19, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 1.7% (30-day exploitation probability)+11
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

1.68%

ahead of 77% of scored CVEs · Oct 19, 2026

Affects

Tautulli

CVSS base

7.2

High · 3 source(s)

Prioritization reference: 8.1 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Tautulli Tautulli).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Tautulli	Tautulli	version < 2.16.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Tautulli	Tautulli	< 2.16.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.1	CVSS 3.1	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
8.0	CVSS 3.1	High	1.3	6.0	security-advisories@github.com via NIST National Vulnerability Database
7.2	CVSS 3.1	High	1.2	5.9	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.1 (GitHub_M via CVE Program (cve.org) e CISA ADP) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · tautulli/tautulli
Oct 19, 2026 · NIST National Vulnerability Database
CVSS changed · 8.1 → 7.2
Oct 19, 2026 · NIST National Vulnerability Database
Source status changed · Published → Analyzed
Oct 19, 2026 · NIST National Vulnerability Database
Record published
Oct 19, 2026
Affected products added · tautulli/tautulli
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
CVSS changed · 8.1
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Published
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Record created in this database
Oct 19, 2026 · Alertas do Telegram
2025
CVE published
Sep 9, 2025 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

1 on the record

github.com/Tautulli/Tautulli/security/advisories/GHSA-jrm9-r57q-6cvf
x_refsource_CONFIRM, Exploit, Vendor Advisory, CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Tautulli
every CVE for this vendor

Injection
same class

CWE-78
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-54915 Tautulli: Open redirect via whitespace bypass in /auth/redirect 28d
High CVE-2026-52835 Tautulli: Path traversal / arbitrary file write via unsanitized upload filename in import_config and import_database 28d
Medium CVE-2026-49995 Tautulli: Stored Cross-Site Scripting (XSS) in the newsletter 28d
Medium CVE-2026-45381 Tautulli: Reflected XSS in `/search` endpoint 28d
Critical CVE-2026-43986 Tautulli vulnerable to unauthenticated SSRF in /image/<hash> via attacker-seeded image hash replay Jun 4, 2026
High CVE-2026-43985 Taultulli has CSRF in /configUpdate via missing anti-CSRF and method restriction that allows admin credential takeover Jun 4, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-58763 is "Tautulli vulnerable to Authenticated Remote Code Execution via Command Injection", rated High. It affects Tautulli (Tautulli); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 1.68% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.