QNAP published on November 6 the Plex2Shell advisory and it is not the kind of note a storage vendor usually writes: some customers have told it that their Plex Media Server on the NAS appears to be compromised, and its support team is reviewing it case by case. The cause is a chain of four vulnerabilities in the media server that allows an outsider to execute commands without having any account, and that has been exploited since October 17.
The timeline is what makes the advisory urgent. Researcher Zach Main reported the flaws to Plex on July 27, the fix arrived in early August and the full technical detail was published on October 16. The attacks began the next day. CISA added the four entries to its catalog of exploited vulnerabilities on October 20 and gave US federal agencies three days to update.
What QNAP adds to the Plex advisory is the uncomfortable part: the patch closes the door, it does not clean the house. If the server was reachable from the internet, updating does not remove whatever the attacker has left inside, and the vendor's recommendation is to reinstall the NAS operating system from scratch and then change all credentials.
A chain of four flaws in the media server
Plex2Shell is four vulnerabilities registered as CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656. Each one on its own has limited scope, according to QNAP's own advisory, and the problem appears when they are chained: access to internal functions, leakage of the server's administrator token and writing to the codecs folder.
That combination allows code execution with the permissions of the Plex process. No authentication is required, and the media server usually runs with access to the entire library, to shared folders and, in many home setups, to volumes that also hold backups and documents.
The fix is in Plex Media Server 1.43.3, specifically from build 1.43.3.10861, available in QNAP's App Center. The Plex advisory does not specify the exact day of the patch and the sources covering it split between August 3 and 4, a minor discrepancy that changes nothing for anyone who has to update today.
The flaw found
The Taiwanese vendor confirms that it has received user reports and that its incident response team has verified that the flaw lies only in the third-party application. QTS and QuTS hero, the NAS systems, are not affected by these four vulnerabilities, which limits the problem to those who installed Plex from the App Center or manually.
What the advisory does not say is how many devices are compromised. Plex does not say either. The figure that can be used is the one left by the exploitation in the first week: according to Plex itself, the servers reached have been used to mine cryptocurrencies and to set up proxies, two ways of extracting value from someone else's machine without drawing too much attention.
That pattern explains why the advisory arrives now and not in October. A media server compromised for mining is not noticed through a ransom screen or an encrypted file: it is noticed through the NAS fan running at full load while nothing is playing.
How to tell if your NAS is compromised
QNAP lists three signs that any owner can check without forensic tools. The first is files they do not recognize in the Plex codecs folder, where the chain leaves the code it executes. The second is outbound connections to domains unrelated to the service, with `proxystream.st` as a documented indicator. The third is high, sustained CPU usage with no active playback.
There is a fourth check that the advisory suggests and that almost nobody does: reviewing whether the server was reachable from outside. Plex remote access enabled, port 32400 forwarded on the router or opened automatically by UPnP or by the router's automatic configuration are enough to leave the server on the internet without the owner remembering it.
If the NAS was exposed and ran a vulnerable version, QNAP is explicit about the procedure: keep the Plex logs folder before uninstalling, reinstall the operating system, reinstall Plex from the App Center without restoring the old codecs folder and, finally, change passwords. The guide to reading a CVE and knowing whether it affects you on the site itself helps to order that checklist before touching anything.
The order in which to do it
Updating is the first step and the only one that admits no delay. On a NAS with Plex installed from the App Center the path is short: App Center, My apps, update and then confirm in Plex Web, under Settings and General, that the installed version is 1.43.3.10861 or higher.
The second step is to close the door before investigating. Disabling Plex remote access and removing the port 32400 forwarding puts the server out of the internet's reach while it is being reviewed. For those who need to see their library outside the home, the alternative the vendor recommends is a VPN, not an open port.
The third is the password, and here there is a detail that gets overlooked: you have to sign out all devices on the Plex account before changing it. If the administrator token was exposed, changing the key without invalidating the previous tokens leaves the door open with the new lock.
The fourth step is the most expensive and the one most people are going to skip: reinstalling if there was exposure. A NAS stores backups, family photos, tax documents and sometimes credentials for other services. The nine-layer cybersecurity guide for SMEs describes the same order that applies here: inventory, updating, rotated credentials and a verified backup, not just one that has been made.
A convenient target
A NAS with Plex is the most awkward machine to explain in an incident report: it is on all day, it has access to the data with the most sentimental and legal value in a home and it is usually administered by someone who is not an IT professional. The Plex chain needs nothing exotic, just an unpatched version and a reachable port.
The same pattern was repeated this week with another exposed desktop device: the Ivanti chain in Connect Secure left more than 5,000 devices exposed because the patch was not applied on all of them. The difference is that a corporate firewall has someone watching the CISA catalog, and the living-room NAS does not.
There remains a timeline lesson that applies to any home device. Between the publication of the details on October 16 and QNAP's advisory on November 6, three weeks passed in which the flaw was public, the exploit was available and most owners had no reason to suspect. The advisory arrived when the compromised devices had already been mining in silence for days, and that silence is exactly what we need to learn to listen for.