QNAP is telling NAS owners to update Plex Media Server right away after receiving multiple reports of suspected compromises of customer devices through Plex2Shell, a four-bug chain in Plex that attackers have been exploiting since October. In a security notice dated November 6, QNAP said some users reported their Plex server "appears to have been compromised" and that its support team is helping them, BleepingComputer reported.
Why it matters: a home or small-office NAS often holds years of photos, documents and backups, plus stored credentials for cloud and backup services. QNAP's warning confirms Plex2Shell is landing on NAS hardware, not just standalone media servers. And the update alone isn't enough: if your vulnerable Plex server was reachable from the internet, QNAP says to treat the NAS as potentially compromised.
What Plex2Shell is
QNAP's security team says the flaws are only in Plex Media Server, a third-party app. QTS, QuTS hero and QNAP's other operating systems aren't affected. Affected builds are Plex Media Server 1.43.2 and earlier on any platform. The fix is 1.43.3.10861 or later, which BleepingComputer says Plex released on August 4.
SonicWall's technical breakdown describes the chain like this:
| CVE | What it does (per SonicWall) | CVSS (per SonicWall) |
|---|---|---|
| CVE-2026-96652 | Unauthenticated SSRF in /player/timeline (the entry point) |
8.6 |
| CVE-2026-96655 | SSRF that sends requests to attacker-chosen hosts | 5.3 |
| CVE-2026-96654 | URI injection that reaches internal plugin routes and leaks the Plex owner's admin token | 6.9 |
| CVE-2026-96656 | Arbitrary file write: a malicious library dropped into the Codecs folder | 5.3 |
Plex loads libraries from the Codecs folder without signature checks, SonicWall says, so the planted library runs during transcoding. That gives the attacker a shell as the Plex service user. The researcher who found the chain scored it 9.8 overall, according to BleepingComputer.
Timeline
- July 27: Researcher Zach Main reports the flaws to Plex (BleepingComputer).
- August 4: Plex releases the fixed 1.43.3.10861 build (BleepingComputer).
- October 16: Full technical details go public. In-the-wild exploitation follows within days, first seen against Plex honeypots dropping a cryptominer.
- October 20: CISA adds all four CVEs to its Known Exploited Vulnerabilities catalog and gives federal agencies until October 23 to patch.
- November 6: QNAP warns about suspected NAS compromises.
Plex has said compromised servers were used to mine cryptocurrency and run proxy software that routes other people's traffic through victims' connections, CyberInsider reports. Nobody we read has named a malware family or given a count of affected NAS devices.
What to do now
1. Update Plex. On QNAP, go to App Center → My Apps and update Plex Media Server. Then check the build in Plex Web under Settings → General: it should read 1.43.3.10861 or newer. Plex installs on other NAS brands, PCs and servers need the same build or later.
2. Work out whether you were exposed. You were at risk if any of these applied while you ran 1.43.2 or earlier:
- Plex Remote Access was turned on.
- Port 32400 was forwarded on your router, either manually, through UPnP, or through myQNAPcloud's router settings. Check your router's UPnP table even if you never set up forwarding yourself.
LAN-only installs with no port forwarding are lower risk, and the update is generally enough, according to The Back Room Tech's summary of QNAP's guidance.
3. If you were exposed, look for signs of compromise. QNAP's guidance, as summarized by CyberInsider and SecurityOnline, lists:
- unfamiliar library files in the Plex Codecs folder
- outbound connections to proxystream.st
- sustained high CPU use when nothing is playing
- unknown Plex processes
4. Clean up. Patching doesn't remove payloads. QNAP's remediation steps, per CyberInsider and SecurityOnline:
- If you want QNAP support to investigate, copy the Plex Logs folder first.
- Do a clean reinstall of Plex from App Center, and don't restore the old Codecs folder. BleepingComputer's reading of the notice goes further and includes a clean reinstall of QTS or QuTS hero. If you saw any of the indicators above, that's the safer route. Back up your media to an external drive first.
- Sign out all devices from your Plex account, then change the Plex password, because the admin token may have leaked.
- Change NAS account passwords and rotate any credentials stored on the box, including backup and cloud-sync logins.
5. Close the door. If you only stream at home, turn off Plex Remote Access and remove the port-32400 forward. If you need remote access, QNAP recommends going through a VPN.
What to watch
QNAP says it will review logs from suspected compromises submitted through its support portal. Watch for an indicator list or affected-device count from QNAP or Plex, and for similar warnings from other NAS makers whose app stores carry Plex. The bugs are in Plex itself, so any NAS or server running Plex 1.43.2 or earlier has the same exposure.
Sources
- BleepingComputer — QNAP says hackers breaching NAS devices in Plex2Shell attacks bleepingcomputer.com
- CyberInsider — QNAP warns of ongoing Plex2Shell attacks on NAS devices cyberinsider.com
- SecurityOnline — QNAP Warns NAS Users as Exploited Plex2Shell Vulnerabilities Hit Plex Media Server securityonline.info
- BleepingComputer — CISA: Hackers chain Plex flaws in Plex2Shell attacks to breach servers bleepingcomputer.com
- The Back Room Tech — QNAP urges users to patch Plex2Shell vulnerability as hackers actively exploit NAS devices thebackroomtech.com
- SonicWall — Plex2Shell: Plex Media Server exploit chain, SSRF to arbitrary code execution sonicwall.com