CVE-2026-40605
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.1, a path traversal vulnerability in the cache deletion endpoint allows authenticated API access to delete directories outside the configured cache path. This can cause arbitrary data loss and service disruption. Version 2.17.1 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTautulli prior to 2.17.1 contains a path traversal vulnerability in its cache deletion API endpoint. An authenticated attacker can manipulate the path parameter using '../' sequences to escape the intended cache directory and delete arbitrary directories on the filesystem, leading to data loss and service disruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Tautulli is runningCheck for tautulli processes (ps aux | grep -i tautulli) or look for the web service on port 8181 (curl -s http://localhost:8181)Affected if Tautulli is not running - you are not affected
-
Determine installed Tautulli versionAccess the Tautulli web interface and check the version in the header/menu, or look for a version file in the Tautulli installation directoryAffected if Version is 2.17.1 or later - you are not affected; version is prior to 2.17.1 - continue to next check
-
Check if remote/API access is enabledExamine Tautulli settings under 'General > Security' or check config.xml for 'enable_api' or 'web_server' settingsAffected if Remote access is disabled and API is not exposed - you are likely not affected; remote/API access is enabled - vulnerability is potentially exploitable
-
Verify authentication configurationCheck Tautulli authentication settings in the web interface under 'General > Security' or in config.xml for 'auth' settingsAffected if Authentication is disabled - attack surface differs but version is still vulnerable; authentication is required - an authenticated user could exploit this flaw
You are affected if running Tautulli version prior to 2.17.1 with the API/web interface accessible and an attacker can obtain valid authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Tautulli version 2.17.1 or later. If immediate patching is not possible, restrict API access to trusted users only and monitor for unusual deletion patterns.
2.17.1
- Back up your current Tautulli configuration and data directory
- Stop the Tautulli service
- Download Tautulli version 2.17.1 or later from the official GitHub repository
- Install the upgrade following standard Tautulli upgrade procedures
- Start the Tautulli service
- Verify the service is running and the cache deletion functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data