Plex.tv
We have not found a subprocessor list published by Plex.tv. We monitor 4 of its documents, which we last checked on Nov 11, 2026.
No tracked subprocessors.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors
None extracted.
Web TechnologiesCSV of Plex.tv's web technologies · Atom feed of Plex.tv's web technologies
Plex.tv's homepage made 360 requests to 51 domains, 33 services controlled by another company, and 6 domains not identified.
33 third parties by category: Advertising 16Analytics 4Cookie compliance 1Other 4Unclassified 8
redfastlabs.comadvolve.iocognitivlabs.comhb-vntsm-com.global.ssl.fastly.netredfast.comrtbscale.com
14 tracked companies loaded by the homepage are not in Plex.tv's subprocessor list. A website can use a service without it processing customer data.
Security recordCSV of Plex.tv's security record · Atom feed of Plex.tv's security record
What public security catalogs list for Plex.tv, in their words.
Known exploited vulnerabilities
5 vulnerabilities in Plex.tv's software that CISA lists as exploited in the wild.
| CVE | Product | Vulnerability | Listed |
|---|---|---|---|
| CVE-2026-96652 | Media Server | Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability | |
| CVE-2026-96654 | Media Server | Plex Media Server Improper Neutralization of Encoded URI Schemes in a Web Page Vulnerability | |
| CVE-2026-96655 | Media Server | Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability | |
| CVE-2026-96656 | Media Server | Plex Media Server External Control of File Name or Path Vulnerability | |
| CVE-2020-5741 | Media Server | Plex Media Server Remote Code Execution Vulnerability |
Data breaches
- Plex 327,314 accounts Email addresses; IP addresses; Passwords; Usernames
In July 2015, the discussion forum for Plex media centre was hacked and over 327k accounts exposed. The IP.Board forum included IP addresses and passwords stored as salted hashes using a weak implementation enabling many to be rapidly cracked.
Have I Been Pwned
Source: CISA Known Exploited Vulnerabilities catalog (evidence) Breach data: Have I Been Pwned (CC BY 4.0), which calls every entry a breach, including data scraped from public pages (evidence)
Service statusCSV of Plex.tv's status page incidents · Atom feed of Plex.tv's status page incidents
90 days agotoday
- 13 incidents in 90 days
- 4 major or critical
- 2 h 22 min typical time to resolve
- 2 h 22 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Marketing site is down | no impact stated | 2 h 54 min | |
| 401 responses for Luma requests with proxy token | no impact stated | 10 h 20 min | |
| my-plex pods resolved DB's DNS to old/blue DB instead of new/green one | no impact stated | 3 h 29 min | |
| No AVOD ads on iOS or tvOS | no impact stated | 16 h 1 min | |
| plex.direct name resolution | no impact stated | 2 h 44 min | |
| Outbound connection issue from our prod-us-east-1 kubernetes cluster | no impact stated | 52 min | |
| Watch-Together - Rooms creation failure | major | 17 min | |
| DNS Issues with plex.tv API | critical | 35 min |
Incidents per month
critical major minor no impact stated before or partly before our history
As Plex.tv's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
ChangesCSV of Plex.tv's changes · Atom feed of Plex.tv's changes
None since tracking began.