CVE-2026-96652
Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability
Description
CVE-2026-96652 is a server-side request forgery (SSRF) vulnerability in Plex Media Server that lets an attacker holding any X-Plex-Token value put a full URL into the protocol parameter of /player/timeline and force the server to send a POST request to a destination of their choosing. Because the POST leaves from the Plex Media Server itself, it reaches internal services behind the firewall and carries the server's network identity rather than the attacker's. All Plex Media Server versions before 1.43.3.10861 are affected by CVE-2026-96652. CISA has added this Plex Media Server SSRF vulnerability to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, with a remediation deadline of November 3, 2026.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| plex | media server | < 1.43.3.10861 |
References
- https://forums.plex.tv/t/plex-media-server/30447/711(Release Notes)
- https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json(Third Party Advisory)
- https://www.cve.org/CVERecord?id=CVE-2026-96652(Third Party Advisory, VDB Entry)
- https://zmain.info/blog/plex2shell(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96652(US Government Resource)
Weakness Type
CWE-918: Server-Side Request Forgery (SSRF)
Server-side request forgery occurs when an application issues a request to a user-supplied URL without validating the destination, allowing an attacker to steer the request at internal addresses a firewall was meant to protect. In Plex Media Server, the protocol parameter of the /player/timeline endpoint accepts a complete URL instead of a protocol identifier, and the server dutifully POSTs to it, turning the media server into an outbound request proxy for whoever controls that value.
Learn more: CWE-918 — Server-Side Request Forgery (SSRF)
Impact Analysis
CVE-2026-96652 has a CVSS 3.1 base score of 4.3 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Attack Vector (Network) and Attack Complexity (Low) mean the SSRF is remotely exploitable with a single crafted request and no special conditions. Privileges Required (Low) is the weakest gate in this vulnerability: the description states that any X-Plex-Token value works, so the bar is possession of a token rather than a privileged account, and no user interaction is needed. Confidentiality (Low), Integrity (None), Availability (None): the scored impact is restricted to what the forged request discloses, which is why CVE-2026-96652 stays in the medium band even though it is a POST, not a GET. In practice, the ability to make a trusted internal host POST attacker-chosen data to an attacker-chosen URL matters more than the base score suggests — it can trigger state-changing actions on internal APIs that accept unauthenticated POSTs and can exfiltrate data through the request body. The EPSS score of 0.22% reflects limited observed exploitation of this specific endpoint, while the KEV listing confirms real attacks.
Exploit Maturity
CISA has added CVE-2026-96652 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild; the entry does not flag ransomware usage. The flaw was disclosed as part of the Plex Media Server vulnerability set covered in the public "plex2shell" analysis, which means the endpoint, the parameter and the shape of the request are documented in the open even though no packaged exploit appears in the reference set. With an EPSS score of 0.22% (12th percentile), automated mass exploitation of this specific SSRF is not yet widespread. The scenario worth planning for is chaining within the same unpatched server: an attacker uses CVE-2026-96652 to reach and probe internal services from a trusted host, then escalates through the arbitrary file write CVE-2026-96656, which yields code execution on the Plex Media Server itself.
Remediation
- Carry out the action CISA requires. Apply mitigations in accordance with Plex's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline for CVE-2026-96652 is November 3, 2026.
- Upgrade Plex Media Server to 1.43.3.10861 or later, as published in the Plex release notes. Every build before that release is vulnerable, and the same update also fixes the companion SSRF in
/video/:/transcode/universaland the arbitrary file write disclosed alongside it. - Invalidate existing tokens. Because any
X-Plex-Tokenis sufficient, sign out all devices and rotate the Plex account password so that tokens that have leaked into logs, URLs, browser history or shared configuration stop working. - Restrict the server's outbound paths. Put the Plex host in a segment with no route to management interfaces, hypervisors or cloud metadata addresses such as 169.254.169.254, and apply egress filtering so that a forged POST has no valuable destination even if it is generated.
- Look for evidence and harden the pattern. Check proxy and firewall logs for POST requests originating from the Plex host towards RFC 1918 ranges, loopback or unfamiliar external hosts; in any service you develop, treat a parameter named for a protocol as an enumeration validated against a fixed allowlist, never as a free-form URL, and block private and link-local destinations after DNS resolution.
Technical Details
The /player/timeline endpoint of Plex Media Server accepts a protocol parameter that is expected to name a transport, but the implementation does not constrain it to that set: a complete URL placed in the parameter is used as the destination for an outbound POST issued by the server process. That is the CWE-918 mechanism in its most direct form — a user-controlled value flows into the destination of a server-initiated request without allowlist validation or a check against private address ranges. Authentication is nominally present but ineffective as a control, since the description specifies that any X-Plex-Token value is accepted for this request. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N captures a network-reachable, deterministic flaw requiring only low privileges, with limited confidentiality impact and an unchanged scope, because the affected and impacted component is in both cases the Plex Media Server process even though the forged request crosses into another network zone.
Frequently Asked Questions
Is CVE-2026-96652 being actively exploited?
Yes. CISA has added CVE-2026-96652 to the Known Exploited Vulnerabilities catalog, which reflects confirmed exploitation in the wild, with a federal remediation deadline of November 3, 2026. Use in ransomware campaigns is not recorded, and the EPSS score of 0.22% indicates that broad automated exploitation of this endpoint has not yet been observed.
What products are affected by CVE-2026-96652?
CVE-2026-96652 affects Plex Media Server in all versions before 1.43.3.10861, on every platform the server is distributed for. The vulnerable code is the /player/timeline endpoint in the server, so Plex client applications are not affected. Servers on 1.43.3.10861 or later are fixed.
How do I fix CVE-2026-96652?
Upgrade Plex Media Server to 1.43.3.10861 or newer, which stops the protocol parameter from being used as an arbitrary request destination. Because any X-Plex-Token value is enough to exploit it, also sign out all devices and rotate your Plex credentials to invalidate leaked tokens, and restrict what the Plex host can reach outbound so a forged POST cannot touch internal management interfaces.
How severe is CVE-2026-96652?
CVE-2026-96652 is rated Medium with a CVSS 3.1 base score of 4.3, because the scored impact is limited information disclosure without integrity or availability damage. Its EPSS score of 0.22% places it in the 12th percentile for exploitation likelihood. The rating understates the operational risk on networks where the Plex server can reach sensitive internal services, and the KEV listing makes patching mandatory regardless of the numeric severity.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.