CVE-2026-96652

Plex Media Server before 1.43.3.10861 allows SSRF via '/player/timeline'.

Medium Known exploited

Severity: 5.3 / 10; Medium · CVSS 4.0
Exploit chance (EPSS): 1.82%; Chance of exploitation in the next 30 days. Higher than 78.76% of scored vulnerabilities.
Known exploited: Yes; In CISA's catalog since Oct 20, 2026
Weakness: CWE-918 Server-Side Request Forgery (SSRF)
Fix: None yet; No fixed version published

Exploited in the wild. Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability (Plex Media Server). Required action: 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. Due for U.S. federal agencies by Nov 3, 2026.

Description

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.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 5.3

CVSS: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:X

Attack vector: Network
Attack complexity: Low
Attack requirements: None
Privileges required: Low
User interaction: None
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None
Exploit maturity: Not defined
Scope: X

CVSS 3.1 4.3

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

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Weakness

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

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Advisories

Timeline

Sep 23, 2026 Published
Oct 20, 2026 Added to CISA's Known Exploited Vulnerabilities catalog
Oct 21, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score
Nov 3, 2026 Remediation due for U.S. federal agencies

Advisory	Severity	Why it's related
EEF-CVE-2026-115700 SSRF allowlist bypass via percent-encoded bracketed IPv6 or trailing-dot IP literal in hackney	Not rated yet	Same weakness, CWE-918
GHSA-2wqp-q3c6-ccj5 MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints	Medium	Same weakness, CWE-918
GHSA-2phh-27fw-q4gc PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading	Medium	Same weakness, CWE-918
GHSA-p3pr-8f3m-4qp8 pyLoad WindowsPhoneNotify addon: non-admin SETTINGS user triggers SSRF via unguarded http.client notification host	Medium	Same weakness, CWE-918
GHSA-j8f7-x8jm-wmm4 Langflow: SSRF in URL-taking components (protection disabled by default / warn-only, not applied to RSS, SearXNG, Web Search, Home Assistant, Glean, Docling)	Medium	Same weakness, CWE-918
GHSA-r7f2-6fj8-6fg2 Ghost: Private IP Filtering Bypass via IPv6 Transition Addresses	Medium	Same weakness, CWE-918
GHSA-322m-ff4g-9vx9 Ghost: Server-Side Request Forgery in Bookmark Fetching	Medium	Same weakness, CWE-918
GHSA-cjq9-62q9-8jv4 Next.js has Server-Side Request Forgery in Image Optimization	Medium	Same weakness, CWE-918

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor