dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-43985

HIGH · 8.8 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Versions prior to 2.17.1 expose `configUpdate` as a state-changing administrator endpoint, but the route does not enforce `POST` and does not use any anti-CSRF token. In the default form and JWT-based authentication mode, the administrator session cookie is issued with `SameSite=Lax`, which still permits top-level cross-site navigation requests. An attacker can exploit this by luring a logged-in administrator to a malicious page that submits a cross-site request to `/configUpdate` and overwrites the local administrator username and password. The attacker can then sign in directly with the chosen credentials and take over the Tautulli administrative interface. Version 2.17.1 patches 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 confidence

Tautulli versions before 2.17.1 expose a configUpdate endpoint that lacks POST method enforcement and anti-CSRF token protection. Combined with SameSite=Lax cookies on the administrator session, this allows cross-site request forgery attacks where a malicious page can silently trigger credential changes on behalf of a logged-in administrator.

MitigationUpgrade to Tautulli version 2.17.1 or later which implements proper POST method enforcement and anti-CSRF protections for the configUpdate endpoint.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Tautulli is installed and accessible
    Check if the Tautulli web interface is reachable by accessing the application's login page or admin dashboard via HTTP/HTTPS.
    Affected if Tautulli is running and accessible on the network
  2. Identify the installed Tautulli version
    Log into the Tautulli admin interface and navigate to Settings > About, or check the version displayed on the login page or in the server logs.
    Affected if The displayed version is before 2.17.1 (e.g., 2.17.0, 2.16.x, etc.)
  3. Confirm the /configUpdate endpoint is available
    Verify the endpoint exists by checking if a POST request to /configUpdate is accepted (requires admin authentication). This endpoint handles configuration updates.
    Affected if The endpoint responds and accepts POST requests without additional CSRF token validation
  4. Inspect session cookie SameSite attribute
    Log into Tautulli as admin, open browser developer tools (Application > Cookies), and examine the session cookie for the SameSite attribute.
    Affected if The session cookie has SameSite=Lax or is missing the SameSite attribute entirely

A user is affected if Tautulli is running and the installed version is before 2.17.1, the /configUpdate endpoint is accessible to authenticated admins, and the session cookie uses SameSite=Lax or lacks SameSite protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Tautulli version 2.17.1 or later which implements proper POST method enforcement and anti-CSRF protections for the configUpdate endpoint.

Recommended fix High confidence

2.17.1

  1. 1. Back up your current Tautulli configuration and data directory before upgrading.
  2. 2. Download Tautulli version 2.17.1 from the official GitHub repository (github.com/tautulli/tautulli).
  3. 3. Stop the running Tautulli service.
  4. 4. Replace the existing Tautulli installation files with the new version 2.17.1 files.
  5. 5. Start the Tautulli service.
  6. 6. Verify the application is running correctly and you can access the web interface.
  7. 7. Log in with your existing administrator credentials to confirm the upgrade was successful.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43985 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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