NVD / CVE Program· CNA GitHub_M

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

HighCVSS 7.2 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.1% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
EPSS: 1.6% · 77th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.6%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.2
CNA · GitHub_M: 8.0; 0.8 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
tautulli	tautulli	cpe:2.3:a:tautulli:tautulli

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

Tautulli Tautulli
- < 2.16.0affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

tautulli tautullibefore 2.16.0

Same product

tautulli: all records

Other highest-scoring records for the same primary product.

CVE-2019-19833In Tautulli 2.1.9, CSRF in the /shutdown URI allows an attacker to shut down the remote media server.
60This week
CVE-2026-43986Tautulli vulnerable to unauthenticated SSRF in /image/<hash> via attacker-seeded image hash replay
39Monitor
CVE-2026-43985Taultulli has CSRF in /configUpdate via missing anti-CSRF and method restriction that allows admin credential takeover
35Monitor

Published before and after this one in the same product

← EarlierCVE-2025-58761Sep 9, 2025 · Tautulli vulnerable to Unauthenticated Path Traversal in `real_pms_image_proxy`
30Monitor
← EarlierCVE-2025-58762Sep 9, 2025 · Tautulli vulnerable to Authenticated Remote Code Execution via write primitive and `Script` notification agent
28Monitor
Later →CVE-2026-28505Mar 30, 2026 · Tautulli: RCE via eval() sandbox bypass using lambda nested scope to escape co_names whitelist check
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2025-587600 days apartTautulli vulnerable to Unauthenticated Path Traversal in `/image` endpoint
30Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records