// Güvenlik

Four chained vulnerabilities in Plex Media Server demand an urgent update

Four vulnerabilities affecting Plex Media Server versions prior to 1.43.3.10861 are being actively exploited. CISA added the vulnerabilities to the KEV list; a chain leading to remote code execution can be established.

Plex Media Server, one of the first names that comes to mind when you think of a home theater server, is making headlines with four separate security vulnerabilities. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the vulnerabilities numbered CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656 to its Known Exploited Vulnerabilities (KEV) list on October 20, 2026. Plex also confirmed in an announcement the same day that the flaws were being “actively and widely” exploited, and that heavy attacks on internet-accessible servers began after a proof-of-concept was published on October 16.

The affected version range is broad: all builds of Plex Media Server before 1.43.3.10861 are affected by all four vulnerabilities. The fix was released in early August, so the flaws have been closed in the patched version for months. The problem is that installations that haven’t received the update are still out in the wild.

How four vulnerabilities turn into a single attack

The first link in the chain is CVE-2026-96652. A server-side request forgery (SSRF) flaw in the player timeline endpoint lets an attacker make the server send a POST request to an address of their choice using any X-Plex-Token value, even one that doesn’t carry a valid token. The second link, CVE-2026-96654, provides access to internal agent functions through the loopback interface. The third link, CVE-2026-96655, causes the server owner’s admin token to be exposed. The final link, CVE-2026-96656, allows arbitrary files to be written to the Codecs folder through transcoder preferences; because Plex loads the libraries in that folder when it starts, the written file becomes executable.

Taken individually, these four bugs sit in the medium and high severity ranges, but when combined the picture changes: an unauthenticated attacker can execute code remotely with the privileges of the Plex Media Server process. According to Plex’s statement, compromised servers were used to run cryptocurrency mining and proxy software; in other words, the victim’s internet connection was opened to other people’s traffic.

Who should update immediately

On Windows and macOS, if automatic updates are enabled, it’s enough to verify in the Settings menu that the version is 1.43.3.10861 or later. Linux distributions, NAS devices, and Docker installations don’t receive automatic updates; the package must be downloaded and installed manually. Plex’s announcement includes device-specific installation guides for Synology, QNAP, TerraMaster, WD, and Netgear users. On NVIDIA Shield, the update comes through Google Play.

What to look for if you’re checking the server for traces

Plex recommends treating any server older than 1.43.3.10861 that is accessible from the internet as compromised. The checklist is short: unfamiliar processes started by Plex Media Server (especially names like myawesomeproxy, mylovelyminer, or x12345), foreign .so and .dll files in the Codecs folder, outbound connections to proxystream.st, and high CPU usage while nothing is playing.

If you see any of these signs, or if the possibility of compromise can’t be ruled out, you need to do a clean installation without moving the old Plex data folder. At a minimum, empty the contents of the Codecs folder and check Preferences.xml for transcoder options you didn’t set yourself. Then sign out all device sessions in the Plex account and change the password. Shares accessible by the Plex service account and credentials stored on the same machine should also be considered exposed.

Turn off remote access if you don’t need it

For users who don’t need to watch from outside, the most effective step is to turn off the Remote Access option under Settings and not forward port 32400 to the internet. CISA’s deadlines are as follows: October 23, 2026 for CVE-2026-96656 and CVE-2026-96654, and November 3, 2026 for CVE-2026-96655 and CVE-2026-96652. These dates are binding for U.S. federal agencies; for home users, the takeaway is that the patch should not be delayed.

Source: CISA KEV · Plex Security Advisory

// JOIN THE CONVERSATION

Share your experience

Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.

// KEEP READING

One more note.

All posts ↗︎