Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability
CVE-2026-96652 · Plex Media Server · Published 2026-09-23
How bad would it be?
5.3 out of 10
CVSS rates it medium.
How likely is it to be used?
1.8%
Estimated chance of exploitation in the next 30 days, higher than 78% of all scored flaws (EPSS, 2026-10-29).
Is it already being used?
Yes
CISA has seen it exploited in real attacks. For US government agencies the fix is due in 4 days (2026-11-03).
What CISA says to do
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Plex Media Server contains a server-side request forgery (SSRF) vulnerability which could allow an attacker using any X-Plex-Token value to include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination. This vulnerability can be chained with CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656.
Plex Media Server before 1.43.3.10861 allows SSRF via '/player/timeline'. An attacker using any X-Plex-Token value can include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination.
Understand the kind of weakness behind this flaw. These resources teach the weakness, rather than reproduce this specific CVE. Follow the vendor's advice above to fix the affected product.
Server-side request forgery
Input makes a server send a request to an unintended destination.
Exploited flaws from CISA's KEV catalogue. Chance of exploitation from EPSS by FIRST. Descriptions and scores from the NVD. This product uses the NVD API but is not endorsed or certified by the NVD.