Act nowVulnerabilities

Plex2Shell: four Plex Media Server flaws are being exploited

CISA added four Plex Media Server flaws to its list of exploited vulnerabilities on 20 Oct 2026. Press reports say attackers install crypto miners. What to check, even if you never use Plex.

Updated 8 Nov 2026: see what changed

How urgent

Act now

Who is affected

Anyone running Plex Media Server that is reachable from the internet, version 1.43.2 or earlier according to press reports

What to do

Update Plex Media Server to 1.43.3 or later, check it is not exposed to the internet unnecessarily, and look for unknown processes

Published 22 Oct 2026 · Sources last checked 8 Nov 2026No. 6 / 87

Updates, follow-ups and corrections

  1. Update · 8 Nov 2026. QNAP says some of its NAS owners reported that Plex Media Server on their device appears to have been compromised through the Plex2Shell flaws (BleepingComputer, 6 Nov; we could not open QNAP's own advisory). QNAP says the flaws are in Plex Media Server only, not in QTS, QuTS hero or its other operating systems, and tells owners to update Plex from the App Center to the latest version, currently 1.43.3.10861. If the App Center does not show it yet, do not assume you are current: open Plex's Settings, General and check the installed build is 1.43.3.10861 or newer, or install the package manually.
  2. Update · 27 Oct 2026. Plex's own advisory now confirms it, and gives the exact build. A post dated 19 Oct says the flaws are "actively and widely exploited" and that Plex Media Server 1.43.3.10861 and later are not affected, so that is the number to look for (Settings, General). For servers older than that and reachable from the internet, Plex tells owners to look for unfamiliar processes, unknown .so or .dll files in the Codecs folder, connections to proxystream.st and high CPU use while idle. If you find signs, or cannot rule them out, rebuild from a clean install, clear the Codecs folder, check Preferences.xml for unexpected transcoder options, sign out all devices and change your Plex password. If you do not need remote access, turn it off and do not forward port 32400.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 20 October 2026 CISA, the US cybersecurity agency, added six vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary to its Known Exploited Vulnerabilities catalog, the list of flaws it has evidence that attackers are using. Four of them are in Plex Media Server:

  • CVE-2026-96652, server-side request forgery.
  • CVE-2026-96654, improper handling of encoded web addresses.
  • CVE-2026-96655, server-side request forgery.
  • CVE-2026-96656, external control of a file name or path.

The other two are in EG Secure Solutions SiteGuard Server Edition (CVE-2026-106931, operating system command injection) and Siemens Software Center (CVE-2026-110936, uncontrolled search path). CISA's alert gives no due date for any of the six, and reminds everyone that it encourages all organisations to prioritise the flaws on this list.

What we could confirm, and what we could not

CISA's alert confirms the list above. The rest comes from press reports, and we could not open Plex's own advisory:

  • The four Plex flaws are being called Plex2Shell. Chained together, reports say they allow code to run on the server without a login.
  • Reports say details and sample attack code became public on 16 October 2026, and attackers went after exposed servers within about a day, installing cryptocurrency-mining and proxy software.
  • Reports give 1.43.2 and earlier as affected and 1.43.3 as the fix. Different outlets quote different build numbers for the fix, so check the number on Plex's own site.

What to do

  1. If you run Plex Media Server, update it to 1.43.3 or later, and update the Plex desktop app too. Reports say there is no workaround. If you use a NAS or Docker, the package for your device may be behind, so update by hand if needed.
  2. Check whether your server is open to the internet. If Remote Access is on or port 32400 is forwarded and you do not need it, turn it off.
  3. Look for what should not be there: unfamiliar processes, scheduled tasks or unexpected high CPU use.

Even if you never use Plex

Our advice, not from CISA: the lesson is the speed. According to the reports, attackers started using these flaws about a day after the details became public. Any server you run that faces the internet, for a small team or a side project, needs an owner and a habit of applying updates quickly. Keep a short list of what runs where and who updates it.

Terms explained in this article

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks