# CVE-2026-31804: Tautulli: Unauthenticated pms_image_proxy endpoint proxies arbitrary HTTP requests through the Plex Media Server

> Unauthenticated attackers can force Tautulli to proxy arbitrary HTTP requests via Plex Media Server, enabling access to internal network resources.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-qj2f-4c4p-wv97

## What is CVE-2026-31804?

CVE-2026-31804 is a medium-severity server-side request forgery vulnerability in Tautulli, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the /pms_image_proxy endpoint accepts a user-supplied img parameter and forwards it to Plex Media Server's /photo/:/ transcode transcoder without authentication and without restricting the scheme or host. The endpoint is intentionally excluded from all authentication checks in webstart.py, any value of img beginning with http is passed directly to Plex, this causes the Plex Media Server process, which typically runs on the same host or internal network as Tautulli, with access to RFC-1918 address space, to issue an outbound HTTP request to any attacker-specified URL. This issue has been patched in version 2.17.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-31804?

It affects 1 product.


Products: Tautulli Tautulli.

## How do I fix CVE-2026-31804?

No fix has been published for CVE-2026-31804 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31804 being exploited?

There is no known exploitation of CVE-2026-31804 in the wild and no public exploit code.

## Other vulnerabilities in Tautulli

- [CVE-2025-58762](https://insights.sbomify.com/CVE-2025-58762/): Tautulli vulnerable to Authenticated Remote Code Execution via write primitive and `Script` notification agent (critical 9.1)
- [CVE-2026-31831](https://insights.sbomify.com/CVE-2026-31831/): Tautulli: Unauthenticated Path Traversal in `/newsletter/image/images` endpoint (high 8.7)
- [CVE-2025-58760](https://insights.sbomify.com/CVE-2025-58760/): Tautulli vulnerable to Unauthenticated Path Traversal in `/image` endpoint (high 8.6)
- [CVE-2025-58761](https://insights.sbomify.com/CVE-2025-58761/): Tautulli vulnerable to Unauthenticated Path Traversal in `real_pms_image_proxy` (high 8.6)
- [CVE-2025-58763](https://insights.sbomify.com/CVE-2025-58763/): Tautulli vulnerable to Authenticated Remote Code Execution via Command Injection (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31804 and fix it if it is affected.

What it is: CVE-2026-31804 is a medium-severity server-side request forgery vulnerability in Tautulli, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31804 in the wild and no public exploit code.

Affected product: Tautulli. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31804/ (Markdown: https://insights.sbomify.com/CVE-2026-31804/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31804
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31804
- OSV: https://osv.dev/vulnerability/CVE-2026-31804

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31804/
Summaries are generated and may contain mistakes; the official description above is the record.