Key takeaways
- Update Plex Media Server to 1.43.3.10861 or later. Versions 1.43.2 and earlier are affected by the four Plex2Shell flaws.
- Confirm the version in Plex Web under Settings, General. A download that never installed does not protect you.
- If an old version was reachable from the internet, treat the server as possibly compromised. Updating does not remove anything an attacker installed.
- Plex lists four signs to look for: odd processes started by Plex, unfamiliar .so or .dll files in the Codecs folder, connections to proxystream.st, and high CPU while nothing plays.
- If you do not need remote access, turn it off and do not forward port 32400. If you need it, QNAP advises a VPN.
On this page
- What you need
- What Plex2Shell is, in plain words
- The four vulnerabilities
- Step 1: Update Plex Media Server
- Step 2: Decide whether you need to check for compromise
- Step 3: Check for signs of compromise
- Step 4: Stop exposing Plex to the internet
- Common questions for experienced users
- Troubleshooting
- What is confirmed and what is not
The Plex security update you need is Plex Media Server 1.43.3.10861 or later. Versions 1.43.2 and earlier have four flaws, nicknamed Plex2Shell, that Plex says are "being actively and widely exploited." Update first, then check whether the server was already hit, then stop exposing it to the internet if you do not need to.
This guide is written for people who run Plex on a NAS at home, such as a QNAP box, but the checks work on any machine that runs Plex Media Server.
What you need
- Access to the machine that runs Plex Media Server, such as your QNAP NAS and its App Center.
- Access to Plex Web, to read the version under Settings, then General.
- To know whether Remote Access was on, whether port 32400 was forwarded on your router, and whether UPnP may have opened it. If you are not sure, Step 2 tells you what to do.
- Your Plex account sign-in, in case you need to sign out of all devices and change your password in Step 3.
What Plex2Shell is, in plain words
Plex Media Server is the program that stores your films and music and streams them to your TV or phone. On a NAS it runs as an app, with access to the shared folders where your media lives.
Plex2Shell is a chain of four bugs. On its own, each bug is limited. Chained together, Plex says they let "an unauthenticated remote attacker run code with the privileges of the Plex Media Server process." In plain terms: someone on the internet, with no password, can make your Plex server run their program.
According to Plex's security post, attackers have used hijacked servers to run cryptocurrency miners and proxy software that routes other people's traffic through your connection. A public proof of concept was released on 16 October.
The four vulnerabilities
Plex describes each one as follows. The CISA column shows the date each was added to CISA's Known Exploited Vulnerabilities catalog.
| CVE | What it does (Plex's description) | Added to CISA KEV |
|---|---|---|
| CVE-2026-96652 | Unauthenticated server-side request forgery in the player timeline endpoint | 20 Oct 2026 |
| CVE-2026-96654 | Access to internal agent functions over the loopback interface | 20 Oct 2026 |
| CVE-2026-96655 | Disclosure of the server owner's admin token | 20 Oct 2026 |
| CVE-2026-96656 | Arbitrary file write to the Codecs directory through transcoder preferences | 20 Oct 2026 |
The last one explains why the Codecs folder matters in the checks below. Plex describes CVE-2026-96656 as a file write to the Codecs directory. The NVD record for CVE-2026-96656 says that at startup Plex runs all .so files "without signature, execute bit, or symbol checks." A file dropped there runs every time Plex starts, which is why updating alone does not clean a server.
Step 1: Update Plex Media Server
- Install the update. On a QNAP NAS, QNAP says to update Plex Media Server through App Center, then My Apps. On other systems, update it the same way you installed it.
- Confirm the version. Open Plex Web and go to Settings, then General. The version must be 1.43.3.10861 or later.
- Update Plex Desktop too, if you use it. Plex's 1 September post also recommends updating Plex Desktop to 1.115.0.
- Update the NAS itself. QNAP says QTS and QuTS hero are not affected by Plex2Shell, but still advises keeping the operating system and all installed apps up to date.
Check the version, not just the update button. If the version in Settings, General has not changed, the fix is not running.
Step 2: Decide whether you need to check for compromise
Use this table. The rule comes from both Plex and QNAP's notice of 6 November 2026.
| Your situation | What to do |
|---|---|
| Already on 1.43.3.10861 or later before the attacks, or never reachable from the internet | Update if needed, then go to Step 4 |
| Ran 1.43.2 or earlier with Remote Access on | Treat as possibly compromised: do Step 3 |
| Ran 1.43.2 or earlier with port 32400 forwarded on your router | Treat as possibly compromised: do Step 3 |
| Ran 1.43.2 or earlier and UPnP or router auto-configuration may have opened the port | Treat as possibly compromised: do Step 3 |
| Not sure | Do Step 3 |
QNAP puts it plainly: "updating alone will not remove anything an attacker may have installed."
Step 3: Check for signs of compromise
Plex lists four indicators. Any one of them is a reason to rebuild.
- Processes you do not recognise started by Plex Media Server. Plex names examples including myawesomeproxy, mylovelyminer and x12345.
- Unfamiliar .so or .dll files in the Plex Codecs folder.
- Outbound connections to proxystream.st.
- Sustained high CPU use while nothing is playing.
A worked example: you open your NAS resource monitor on a quiet evening. Nobody is watching anything, yet a process under the Plex service sits near full CPU and has a name you have never seen. That matches two of Plex's indicators. Do not just stop the process and carry on; follow the rebuild steps below.
If you find anything, or cannot rule it out
- Keep the evidence if you are on QNAP. QNAP says to preserve the Plex Logs folder before removing Plex Media Server, then open a case with QNAP Technical Support.
- Rebuild from a clean install. Plex says not to reuse the old Plex data directory. At minimum, delete everything in the Codecs folder and check Preferences.xml for transcoder options you did not set.
- Reset your Plex account. Sign out of all devices in your Plex account settings and change your Plex password. QNAP also says to reset your NAS credentials.
- Assume wider exposure. Plex says to treat anything the Plex service account could reach as potentially exposed, including mounted shares and credentials stored on the same machine or VM.
Step 4: Stop exposing Plex to the internet
The attacks hit servers that were reachable from the internet and not updated. Reducing exposure is the part of this advice that stays useful after Plex2Shell.
- If you do not need remote access, turn it off. Plex says: "If you don't need remote access, turn it off under Settings → Remote Access."
- Do not forward port 32400 unless you need it. Plex advises avoiding forwarding port 32400 directly, and QNAP says not to forward it if you do not need remote access.
- Check your router for UPnP. QNAP's notice names UPnP and router auto-configuration as ways the port can be opened without you doing it by hand.
- If you need remote access, use a VPN. That is QNAP's advice: connect to your home network through a VPN, and reach Plex from inside it.
Common questions for experienced users
Why is an unauthenticated chain possible if one bug needs admin rights?
NVD rates CVE-2026-96656 as needing high privileges on its own (CVSS v3.1 7.2, v4.0 8.6). Plex's list shows why that does not save you: Plex describes CVE-2026-96655 as disclosing the owner's admin token and CVE-2026-96652 as an unauthenticated request forgery bug. Plex says the full chain gives code execution to an unauthenticated remote attacker. NVD and CISA describe some of these CVEs differently (NVD, for example, rates CVE-2026-96652 as needing a Plex token); Plex's description of the chain is the one that matters for the fix.
Should I wait for a newer Plex release?
No. QNAP says later Plex releases will be made available once verified, and that users should not wait for them before updating.
Troubleshooting
The version in Settings, General has not changed
The fix is not running. Repeat the update from Step 1 and check the version again. It must read 1.43.3.10861 or later.
You are not sure whether the server was exposed
Do Step 3. Plex and QNAP both say to treat a server that ran 1.43.2 or earlier and was reachable from the internet as possibly compromised.
You updated, but you see an odd process or an unfamiliar file
Updating alone will not remove anything an attacker installed. Follow the rebuild steps in Step 3: clean install, empty Codecs folder, account reset.
A newer Plex release is not in App Center yet
Do not wait for it. QNAP says users should update to 1.43.3.10861 or later now.
What is confirmed and what is not
- Confirmed by Plex: the four CVEs, the fixed version 1.43.3.10861, active and wide exploitation, the four indicators of compromise and the rebuild steps.
- Confirmed by QNAP: the NAS operating systems are not affected, the App Center update path, and that QNAP "has confirmed that no data loss has occurred" for the affected users its support team is assisting.
- Confirmed by CISA: all four CVEs are in the Known Exploited Vulnerabilities catalog, added 20 October 2026.
- Not stated by the vendors: how many servers were compromised, and exact Codecs folder paths for each operating system. Plex's post does not give per-system paths.
Keeping software patched is the same habit on every device. If you also want to check your phone, see how to check your Android security patch level. More security explainers are in Dexaloop Tech.
Questions
What is Plex2Shell?
It is the public nickname for a chain of four Plex Media Server vulnerabilities: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656. Plex says they can be chained so that an unauthenticated remote attacker can run code with the privileges of the Plex Media Server process.
Which Plex version fixes Plex2Shell?
Plex says Plex Media Server 1.43.3.10861 and later are not affected. Versions 1.43.2 and earlier are affected. Plex's earlier 1 September post also recommends Plex Desktop 1.115.0, which it says fixes a number of security issues.
Is my Plex server compromised?
If it ran 1.43.2 or earlier and was reachable from the internet, Plex and QNAP both say to treat it as possibly compromised. Look for unknown processes started by Plex, unfamiliar .so or .dll files in the Codecs folder, outbound connections to proxystream.st and sustained high CPU while nothing is playing.
Is the QNAP operating system itself affected?
No. QNAP says the flaws are only in Plex Media Server and that QTS, QuTS hero and other QNAP operating systems are not themselves affected. QNAP still advises keeping the NAS operating system and all apps up to date.
Do I need to close port 32400?
If you do not need remote access, yes. Plex says to turn remote access off under Settings, Remote Access, and to avoid forwarding port 32400 directly unless you need it. QNAP says to use a VPN if you do need remote access.
Is Plex2Shell in the CISA Known Exploited Vulnerabilities catalog?
Yes. CISA's catalog lists all four Plex Media Server CVEs, each with a date added of 20 October 2026.
Sources
- Important Security Update for Plex Media Server v1.43.2 and earlier (Plex forum, PlexInfo) (accessed 9 November 2026)
- QNAP Security Notice: Plex Media Server Vulnerabilities (Plex2Shell), 6 Nov 2026 (accessed 9 November 2026)
- Known Exploited Vulnerabilities Catalog, Plex entries (CISA) (accessed 9 November 2026)
- CVE-2026-96656 detail (NIST National Vulnerability Database) (accessed 9 November 2026)
Written from the sources above and checked against them before publishing. Found a mistake? Email support@dexaloop.com and we will correct it.
More in Security and privacy
- Leaked API key: what to do first, and why deleting the commit is not enough
- Will quantum computers break RSA-2048? What the 22,593-qubit estimate does and does not mean
- pull_request_target vs pull_request: what it does, why GitHub is blocking it, and how to use it safely
- How to check Android security patch level, and what the date means