~/exploited / cve-2026-96652
CVE-2026-96652: Plex Media Server
According to CISA this vulnerability is already used in attacks (added on 20 October 2026).
Key facts
| CVE | CVE-2026-96652 |
|---|---|
| Vendor | Plex — Media Server |
| Vulnerability | Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability |
| Added | 20 October 2026 |
| Deadline (US agencies) | 3 November 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 5.3 (medium) · CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XAttack over the network, complexity: low, privileges: low needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 11.89%. Higher than 96.2% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks. |
| Weakness type (CWE) | CWE-918 — Server-Side Request Forgery |
| Affected versions | media server: < 1.43.3.10861 |
Description (NVD)
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.
Description (CISA)
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.
Required action (CISA)
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.
What admins should do now
- Affected? Check whether Plex Media Server is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 20 October 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
- CISA KEV Catalog
- NVD CVE-2026-96652
- forums.plex.tv/t/important-security-update-for-plex-media-server-v1-43-2-and-ear
- www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-base
- www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizi
- nvd.nist.gov/vuln/detail/CVE-2026-96652
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).