Plex2Shell is the name researchers have given to a chain of four vulnerabilities in Plex Media Server that, combined, let an attacker run code on a server without logging in. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has now added all four flaws to its Known Exploited Vulnerabilities (KEV) catalog and ordered federal agencies to patch by October 23 and November 3, 2026, after reports that attackers are actively exploiting them to install cryptocurrency miners and proxy malware on home and small-business servers.
If you run Plex Media Server at home, on a NAS, or on a VPS, this one is worth your attention today: the flaws were patched back in August, but many servers never update on their own, and attacks were observed in the wild just a day after the exploit details went public.
What is Plex2Shell?
Plex2Shell is an exploit chain described by security researcher Zach Main. It strings together four separate bugs in Plex Media Server, and while none of them is a catastrophe on its own, together they add up to unauthenticated remote code execution. That is what makes this case unusual: individually, the CVEs score from medium (around 4.3) up to high (up to about 8.6, depending on the scoring source), but the chain needs no valid login at all.
Here is what each flaw does:
- CVE-2026-96652 (SSRF): a server-side request forgery in a player endpoint. The endpoint checks that a token exists, but not that it is valid.
- CVE-2026-96654 (URI scheme handling): improper neutralization of encoded URI schemes, used to reach an internal plugin API through the loopback interface.
- CVE-2026-96655 (SSRF): a second server-side request forgery, this time in the transcoder path.
- CVE-2026-96656 (file path control): an admin-level file write that the server later loads as code, which is the final step that turns the chain into code execution.
Put together, the chain effectively steals the server owner’s admin token and then runs commands as the Plex service user. All four flaws affect Plex Media Server before version 1.43.3.10861, across all platforms, including NAS packages and container images. Plex Desktop is a separate product and was not named in these CVE records.
Timeline: from report to real-world attacks
The sequence of events moved fast, which is why CISA is treating this as urgent:
- July 2026: Zach Main reports the four flaws to Plex.
- August 3, 2026: Plex releases Media Server 1.43.3.10861 fixing all four.
- September 1, 2026: Plex publishes a security notice warning users on older versions.
- October 16, 2026: the Plex2Shell write-up and exploit code go public.
- October 17, 2026: a honeypot run by security researcher boredhackerblog records in-the-wild attacks from multiple IP addresses, deploying an XMRig miner called “mylovelyminer” and a Linux backdoor named “myawesomeproxy.”
- October 19, 2026: Plex warns that exploitation is active and widespread.
- October 20-21, 2026: CISA adds all four CVEs to the KEV catalog and sets patch deadlines.
The gap between the public exploit release and the first recorded attacks was roughly one day. The payloads are linked to the AISURU botnet infrastructure, and researchers note that the proxy backdoor gives attackers a residential IP they can use to bounce further attacks.
What CISA is demanding
CISA’s KEV catalog is not a recommendation list: for federal civilian agencies, patching entries by the deadline is mandatory. In this batch, CVE-2026-96654 and CVE-2026-96656 must be fixed by October 23, 2026, and the remaining entries by November 3, 2026. The same KEV update also flagged two other actively exploited flaws:
- CVE-2026-110936 (CVSS 8.4): a DLL sideloading bug in Siemens Software Center, abused in ClickFix attacks. We covered that incident separately.
- CVE-2026-106931 (CVSS 8.5): a command injection flaw in EG Secure Solutions’ SiteGuard Server Edition, which the vendor has confirmed is being exploited.
Even if you are not a federal agency, these deadlines are a useful signal of priority. KEV entries are added only when there is real-world exploitation, so this batch is effectively a confirmed-active-threat list. The same pattern shows up constantly in enterprise software, as our coverage of the Citrix NetScaler SAML flaw shows. And it is arriving in the middle of a brutal October for defenders, with critical fixes like the emergency PHP patches released today also demanding attention.
How to check if your Plex server is at risk
Open your Plex Media Server dashboard and go to Settings, then General, and look at the version number. If you are on anything older than 1.43.3.10861, you are running a vulnerable build. Linux, NAS, and Docker installs do not update themselves automatically, so do not assume your server is current.
Also check whether your server is reachable from the internet. Many people forward port 32400 on their router so friends and family can stream remotely. That is exactly the exposure attackers scan for.
What to do right now
1. Update to 1.43.3.10861 or later
This is the only real fix. On Windows and macOS with automatic updates enabled, check for updates in Settings and install the latest build. On Linux, NAS, or Docker, update the package or image manually through your normal update process. Plex’s own guidance is direct: all server owners should update as soon as possible.
2. Treat older internet-facing servers as possibly compromised
Plex says a server older than 1.43.3.10861 that was reachable from the internet should be treated as one that may already be compromised. That means more than just updating: do a clean reinstall, clear the Codecs folder, and check Preferences.xml for unexpected transcoder options. Look for unfamiliar child processes, Docker containers, or proxy software running alongside Plex, and for the attack indicators researchers published: unexpected .so files in the Codecs directory, mining traffic to the attacker’s pool, and connections to the hostile IPs tied to the campaign (45.194.92.222, 91.92.40.202, 176.65.139.228, and 217.60.194.116).
3. Rotate your credentials
Sign out all devices in your Plex account settings and change your Plex password. If the chain was used against your server, the attacker’s path ran through your admin token, so stale sessions should not be left in place.
4. Stop exposing port 32400 directly
Until you are patched, remove the direct internet exposure of TCP 32400. If you still need remote access, put the server behind a VPN or restrict access to trusted networks, and block outbound connections from the Plex host to arbitrary internet addresses.
Why this one matters more than the scores suggest
On paper, these CVEs look moderate. In practice, the chain is what counts: four medium and high bugs, none of them exotic, combine into a login-free takeover of a box that sits in millions of homes, often on hardware that is rarely maintained. Media servers are attractive targets for exactly this reason: they are always on, they have decent bandwidth and CPU, and they sit on residential IPs that attackers value for proxying. The XMRig miner and the proxy backdoor are just the first payloads; once code execution is available, anything can be deployed next.
Plex fixed this promptly and warned users clearly. The risk now sits entirely with unpatched servers, and CISA’s deadlines are a reminder that the exploitation is real, current, and expected to continue. For background on the Siemens flaw that landed in the same KEV batch, see our Siemens Software Center write-up. Check your Plex version today.
FAQ
What is Plex2Shell?
Plex2Shell is an exploit chain combining four vulnerabilities (CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656) in Plex Media Server that together allow unauthenticated remote code execution. It was disclosed by security researcher Zach Main in October 2026.
Is Plex2Shell being exploited in the wild?
Yes. Attacks were recorded on October 17, 2026, one day after the public exploit release, deploying a crypto miner and a proxy backdoor. CISA added all four CVEs to its Known Exploited Vulnerabilities catalog on October 20-21, 2026.
Which Plex Media Server version fixes Plex2Shell?
Version 1.43.3.10861, released August 3, 2026. Any older build is vulnerable. Linux, NAS, and Docker installations must be updated manually.
What if my Plex server was reachable from the internet and unpatched?
Plex advises treating it as possibly compromised: perform a clean reinstall, clear the Codecs folder, inspect Preferences.xml for tampered transcoder settings, sign out all devices, and change your Plex password.
What are the CISA patch deadlines?
Federal agencies must remediate CVE-2026-96654 and CVE-2026-96656 by October 23, 2026, and the rest of the batch, including the other two Plex CVEs, by November 3, 2026. Private users should patch immediately rather than waiting.