Plex2Shell hits QNAP NAS: real compromises and remediation
QNAP reports NAS devices compromised via Plex2Shell in Plex Media Server: if it was exposed online, update, reinstall cleanly and reset all passwords.

On 6 November 2026 QNAP published an advisory on Plex2Shell, the chain of four vulnerabilities in Plex Media Server (CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656) whose mechanics and addition to the CISA KEV catalog ARX News has already covered. What is new is that exploitation is no longer limited to researchers’ honeypots: the Taiwanese vendor has received reports from some users whose Plex Media Server, installed on their NAS, appears to have been compromised through these flaws, and its technical support is assisting them. The story was covered by BleepingComputer, SecurityWeek, Security Affairs and heise.
What QNAP says
- The problem is only in Plex. QNAP PSIRT confirmed that the vulnerabilities exist only in Plex Media Server: QTS, QuTS hero and the other QNAP operating systems are not themselves affected. Plex is a third-party application that users install from the official App Center.
- Number of victims unknown. The advisory mentions “some users”, with no figures. According to SecurityWeek, quoting QNAP, technical support has confirmed that no data loss occurred; the other sources do not report this detail.
- Fixed version. The version currently available in the App Center is 1.43.3.10861, the one that fixes the chain. According to Security Affairs, QNAP will release further updates once it has verified them, but users should not wait for them.
According to SecurityWeek, widespread exploitation of the chain began in mid-October, after the technical details and proof-of-concept code were published. No valid credentials are needed, and the attacker’s code runs with the privileges of the Plex service.
When to treat the NAS as compromised
The most useful part of the advisory is the criterion for working out who needs to worry. As Security Affairs reports, a NAS should be considered potentially compromised if Plex was reachable from the internet while running version 1.43.2 or earlier. That happens in three cases:
- Plex Remote Access was enabled;
- port 32400 was forwarded on the router;
- the port was opened automatically through UPnP or the router settings.
The third case is the trickiest: a NAS can be exposed without anyone ever opening a port by hand. BleepingComputer reports an even firmer instruction: under these conditions QNAP asks users to treat the NAS and all the personal content on it as compromised.
Updating closes the flaws but does not remove anything an attacker has already installed. The payloads documented so far in public analyses were a cryptocurrency miner and proxy software, as described in our first article; no source says what was found on the compromised QNAP devices.
The sources differ on reinstallation
The three outlets whose text we have agree on updating, checking for signs of compromise and changing passwords, but describe the reinstallation differently: BleepingComputer refers to a clean reinstall of the NAS operating system (QTS or QuTS hero), SecurityWeek to reinstalling Plex, and Security Affairs points to QNAP’s FAQ “Plex2Shell: Check and Remediation FAQ for QNAP NAS Users”. QNAP’s step-by-step guide is therefore the reference. As a precaution, on a NAS that stayed exposed with a vulnerable version, reinstalling the whole operating system is the safest option.
Impact for European and Italian companies
QNAP NAS devices are common in professional firms, small businesses and the homes of remote workers, often as a document store and as a backup target. Plex is installed for media streaming, usually outside IT processes: on a company NAS it may have been added by an individual, with remote access switched on for convenience. A compromised NAS that holds backups is a problem that goes beyond Plex, because it calls into question the very copies you rely on to recover.
For entities in scope of NIS2, a compromised NAS on the company network should be assessed as a possible incident to notify to CSIRT Italia at ACN. If the NAS holds personal data, a GDPR breach assessment is also needed.
What to do now
- Look for Plex on your NAS devices: in App Center, under My Apps, check whether Plex Media Server is installed, including on NAS devices at branch offices and at the homes of people working remotely with company data.
- Update Plex Media Server from the App Center to 1.43.3 or later, then check in Plex Web (Settings, General) that the version is 1.43.3.10861 or later. Also update QTS or QuTS hero and all other installed apps.
- Check exposure: Plex Remote Access, forwarding of port 32400 and UPnP rules on the router. If remote access is not needed, disable Remote Access and do not forward the port; if it is needed, use a VPN.
- If Plex was exposed while running 1.43.2 or earlier: follow QNAP’s FAQ to look for signs of compromise and reinstall from scratch, then immediately change the Plex and NAS passwords.
- Get help from QNAP: according to BleepingComputer, the company offers to analyse logs from suspected cases, submitted through its technical support portal.
- Check your backups: before restoring, make sure you have a copy of the data outside the NAS and not reachable from it.
How ARXDOME helps
ARX Watch finds devices on the network that have no probe installed, such as NAS devices, and flags every new one: it helps you know which NAS devices are really in the company. ARX Expose shows which services the company exposes on the internet and which products with known vulnerabilities are recognised on them: it helps uncover a Plex service reachable from outside, even when the port was opened automatically. On computers and servers with the ARXDOME agent, ARX Sentry collects the inventory of software, processes and ports, which is useful for finding Plex installations outside the NAS.
Last updated:


