Security

Plex2Shell: four-flaw chain is being used to hack QNAP NAS boxes

Key takeaways

  • Update Plex Media Server to 1.43.3 or later via the QNAP App Center and verify 1.43.3.10861 or later in Plex Web
  • Any NAS that exposed Plex on version 1.43.2 or earlier should be treated as compromised, since updating does not remove malware
  • Disable Plex Remote Access and stop forwarding port 32400; use a VPN for remote access

What is Plex2Shell, and why is QNAP telling NAS owners to treat some devices as compromised? It is a chain of four vulnerabilities in Plex Media Server that gives an unauthenticated attacker code execution on an exposed server. QNAP says users have reported compromised Plex installations on their NAS devices, and its support team is assisting them.

What Plex2Shell actually is

Plex Media Server is software that makes a household's films, music and other media available across devices. On a QNAP NAS (network-attached storage, a small always-on box that holds files for a home or office), it runs as a third-party app installed through the QNAP App Center.

Plex2Shell is the name given by security researcher Zach Main to a chain of four flaws in that software: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656. A "chain" means no single bug does the damage; each one gives the attacker a stepping stone to the next. Together they allow arbitrary code execution without valid credentials, provided the required conditions are met. The code runs with the privileges of the Plex service, which gives attackers an opportunity to install software and abuse the host.

QNAP's product security team has confirmed the flaws sit only in Plex Media Server. QTS, QuTS hero (QNAP's operating systems) and other QNAP operating systems are not themselves affected. The NAS is the victim's address, not the source of the bug.

How it works

Main's write-up describes a staged attack. The final stage is the easiest to picture. Plex's transcoder, the component that converts media into formats a given device can play, loads codec libraries from a directory. Plex's loader does much the same: according to Main's analysis, it does not check for a "lib" prefix, does not require the execute permission bit, does not verify a signature and does not look for any specific symbol.

That matters because of how Linux loads shared libraries. When a library is loaded, its constructor functions run before anything else happens. A file containing only a constructor and no exported symbols still executes its code on load. The attacker writes a crafted library into the codec directory using the earlier stages of the chain, then triggers a second transcode. Plex re-enumerates the directory, loads the planted file, and the constructor runs as the plex user.

The chain also abuses a transcoding-related setting to influence what gets executed, so the attacker never needs an interactive login first.

Timeline: patched, then published, then exploited

The sequence is the real lesson. Plex was notified of the flaws on 27 July and acknowledged the report on 4 August, awarding a bug bounty. Fixes shipped in September, before any exploit code was public.

On 16 October 2026, Main published technical details and proof-of-concept code. Within a day, researchers saw attackers using the exploit against an internet-facing honeypot, a deliberately exposed decoy system, deploying cryptocurrency-mining malware and proxy software. SecurityWeek reports that widespread exploitation began in mid-October. CISA added the flaws to its Known Exploited Vulnerabilities catalogue on 20 October 2026, giving federal agencies until 23 October 2026 to address them. Readers unfamiliar with that list can see how to check the CISA KEV catalogue.

Here the fix had been released in September, before exploitation took off in mid-October.

Who is exposed and why attackers want these boxes

The attackers observed so far were not after film collections. They installed cryptocurrency miners and proxy software. A NAS is attractive for that: it is powered on around the clock, usually has a decent processor and a stable connection, and tends to be forgotten once set up. Proxy software turns the device into an exit point for other people's traffic, which is useful to criminals who want to hide behind a residential address.

The exposed population is any QNAP user running Plex Media Server 1.43.2 or earlier with the server reachable from the internet. QNAP names three common routes: Plex Remote Access enabled, port 32400 forwarded manually, or the port opened automatically through UPnP or router settings. UPnP, which lets applications ask a router to open ports without the owner's involvement, is the one people forget they have switched on.

QNAP has also said its support team has confirmed that no data loss has occurred among the affected users it has helped, according to SecurityWeek. That is reassuring but not a guarantee for every device.

What the limitations are

Updating is necessary but not sufficient. QNAP is explicit that patching does not remove anything an attacker has already installed. A miner or proxy implant planted before the update will keep running afterwards. That is why the advice for exposed devices is a clean reinstall of Plex, a check for signs of compromise, and a reset of both Plex and NAS credentials.

There is also a lag on the vendor side. QNAP says it will release further updates after verifying them, but tells users not to wait. And the exploit conditions matter: the chain works "provided the required conditions are met", so not every exposed server will fall, though QNAP's guidance is to assume the worst for any that were reachable.

What this means in practice

For anyone running Plex on a QNAP:

  1. Open App Center, go to My Apps and update Plex Media Server to 1.43.3 or later.
  2. In Plex Web, under Settings and General, confirm the installed version is 1.43.3.10861 or later.
  3. If Plex was reachable from the internet on 1.43.2 or earlier, treat the NAS as potentially compromised. Follow QNAP's "Plex2Shell: Check and Remediation FAQ" for a clean reinstall, and rotate Plex and NAS passwords.
  4. Disable Plex Remote Access if it is not needed, and do not forward port 32400. If remote access is required, use a VPN instead.
  5. Keep QTS or QuTS hero and all installed apps up to date.

The UK angle

An office NAS used for staff media is a small risk; one that shares a network with file shares holding customer records is not. Both the NCSC and ICO guidance reward the same habits QNAP is recommending: patching quickly and keeping services off the open internet.

In the US, the CISA catalogue entry and its 23 October 2026 deadline apply formally to federal agencies, but the catalogue is widely used as a prioritisation list by private teams.

Where this is heading

The sequence here, a responsible disclosure, a September fix, a public proof of concept in October, and mining malware on a honeypot within a day, is now familiar. The practical consequence for NAS owners is that "I'll update at the weekend" no longer works for anything reachable from the internet. QNAP says it will release further updates once it has verified them.

Frequently asked questions

What is Plex2Shell?

Plex2Shell is a chain of four Plex Media Server vulnerabilities that lets an attacker run code on an exposed server without valid credentials, with the privileges of the Plex service.

Is QTS or QuTS hero vulnerable to Plex2Shell?

No. QNAP says the flaws exist only in Plex Media Server, not in QTS, QuTS hero or other QNAP operating systems.

Which Plex version fixes Plex2Shell on QNAP?

Update to Plex Media Server 1.43.3 or later through the App Center, then confirm 1.43.3.10861 or later under Settings and General in Plex Web.

Does updating Plex remove an existing infection?

No. If Plex was internet-reachable on 1.43.2 or earlier, QNAP says to treat the NAS as potentially compromised, reinstall cleanly and reset Plex and NAS credentials.

More from Future Technology HQ