dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-43986

CRITICAL · 9.9 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 →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 a public `/image/<hash>` route that resolves attacker-controlled entries from `image_hash_lookup` and replays them through the same server-side image fetch logic used by authenticated image proxying. A low-privilege guest user can seed a malicious external image URL into this lookup table and then trigger server-side fetches through a fully unauthenticated endpoint. This turns an authenticated SSRF primitive into a persistent unauthenticated SSRF gadget. Once the malicious hash entry exists, any external user can request `/image/<hash>.png` and cause the PMS or Tautulli host to fetch an arbitrary attacker-chosen URL. 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 public /image/<hash> endpoint that resolves attacker-controlled entries from an image_hash_lookup table. A low-privilege guest user can inject malicious external URLs into this lookup table, then trigger unauthenticated server-side fetches through the public endpoint, enabling persistent SSRF attacks against the PMS or Tautulli host.

MitigationUpgrade Tautulli to version 2.17.1 or later to patch the unauthenticated SSRF vulnerability.

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

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

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. Identify Tautulli version
    Locate the Tautulli installation and check its version (typically via the web UI dashboard, about page, or version file in the installation directory). Compare your version number against the affected range (versions before 2.17.1).
    Affected if Your installed version is lower than 2.17.1.
  2. Confirm guest or low-privilege users exist
    Check Tautulli user configuration to see if guest accounts or low-privilege users are enabled. This is typically found in Settings > Users & Authentication or similar user management section.
    Affected if Guest or low-privilege user accounts are active in your Tautulli instance.
  3. Inspect image_hash_lookup table
    Access the Tautulli database (tautulli.db or similar) and query the image_hash_lookup table for any entries containing external URLs. Look for records where the URL field points to non-internal or unexpected domains.
    Affected if The image_hash_lookup table contains URLs pointing to external or unexpected domains.
  4. Verify /image endpoint is publicly accessible
    Attempt to access the /image/<hash> endpoint from an unauthenticated external network connection (or private/incognito browser). Use a known valid image hash if available, or observe whether the endpoint responds without authentication.
    Affected if The /image/<hash> endpoint responds to unauthenticated requests from outside the trusted network.
  5. Review logs for SSRF indicators
    Search Tautulli audit or access logs for requests to /image/ endpoints with external URLs, or for unusual outbound HTTP requests originating from the Tautulli server to unfamiliar destinations.
    Affected if Logs show requests to /image/ endpoints triggering fetches to external or suspicious URLs.

You are affected if running Tautulli before version 2.17.1 with guest or low-privilege users enabled and the image_hash_lookup table contains injected external URLs accessible via the unauthenticated /image/<hash> endpoint.

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 Tautulli to version 2.17.1 or later to patch the unauthenticated SSRF vulnerability.

Recommended fix High confidence

2.17.1

  1. Upgrade Tautulli to version 2.17.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43986 — 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-43986 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