A Movie App Let Strangers Onto QNAP Storage Boxes

Plex Media Server CVE-2026-96656 let attackers onto some QNAP NAS boxes; here's how to check and rebuild your clients' QNAP storage.

Some QNAP storage boxes ended up running strangers' code, and the way in was Plex, the movie app installed beside the files. On 6 November 2026, QNAP said users had reported compromised Plex installs and told owners of internet-facing ones to treat the whole NAS as potentially compromised. Check every client's QNAP box for Plex today.

TL;DR

  • QNAP warned on 6 November 2026 of compromised Plex Media Server installs on its NAS boxes via Plex2Shell, four chained flaws including CVE-2026-96656.
  • Exposed: Plex Media Server 1.43.2 or earlier (see App Center > My Apps) that was reachable from the internet, per QNAP's FAQ.
  • Update Plex to 1.43.3.10861 or later; if it faced the internet, QNAP advises a clean OS reinstall, an emptied Codecs folder and new Plex and NAS passwords.
  • Compromised servers ran crypto miners and proxy software, QNAP's notice says, and its FAQ warns the Plex admin token may have leaked.

What is Plex2Shell and is it being exploited?

Plex2Shell is four chained Plex Media Server flaws, CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656, that let an attacker with no account run code with the Plex app's privileges, according to QNAP. It is being exploited: CISA added all four to its Known Exploited Vulnerabilities (KEV) catalog of attacked bugs on 20 October 2026, with federal due dates of 23 October 2026 for CVE-2026-96654 and CVE-2026-96656, and 3 November 2026 for CVE-2026-96652 and CVE-2026-96655.

CVE-2026-96656 is rated 8.6 (CVSS 4.0); its record describes a file write that needs an admin login, which the chain obtains without one, per QNAP. Our first Plex2Shell article covers the chain; what's new is QNAP's warning.

Which QNAP NAS setups are affected?

A QNAP NAS is affected when it runs Plex Media Server 1.43.2 or earlier, and QNAP says to treat it as potentially compromised if Plex was reachable from the internet on that version, per QNAP's FAQ. The fix is Plex Media Server 1.43.3.10861 or later, in the QNAP App Center. QNAP lists four ways Plex ends up reachable:

  • Remote Access turned on in Plex Web > Settings > Remote Access
  • Port 32400 forwarded on the router
  • UPnP, the feature that lets apps open router ports themselves, on together with Plex Remote Access
  • myQNAPcloud's automatic router configuration, or another method, exposing Plex

A box updated only after the proof of concept appeared, which researcher Zach Main published on 16 October 2026, also counts as potentially compromised if it was exposed. QTS and QuTS hero, QNAP's operating systems, are not affected themselves, QNAP says, but its FAQ treats the shared folders Plex could read as exposed too. QNAP hasn't said how many devices were hit, BleepingComputer notes.

How do I check if my clients' QNAP NAS was hit by Plex2Shell?

Run these in the QNAP console or from a Linux workstation with the PlexData share mounted read-only; none needs a shell on the NAS. On-box logs cover a short period, so search the client's DNS or firewall archive for the full window; a clean on-box result doesn't rule out an earlier break-in. Indicators come from QNAP's FAQ.

  1. Preserve evidence. Download the Helpdesk zip (Helpdesk > Diagnostic Tool > Download Logs) and the event log (Control Panel > QuLog Center > Local device > Event Log > Export Logs), per QNAP, then copy the Plex folders the fix will wipe. Pass: the .sha256 file lists each copied file.

    sudo mkdir -p /mnt/plexdata
    sudo mount -t cifs //<nas-ip>/PlexData /mnt/plexdata -o ro,username=<nas-admin>
    D="$HOME/ir/<client>-$(date +%F)"; mkdir -p "$D"
    P="/mnt/plexdata/Plex Media Server"
    sudo cp -a "$P/Logs" "$P/Codecs" "$P/Preferences.xml" "$D"/
    cp -a ~/Downloads/<helpdesk-logs>.zip ~/Downloads/<qulog-export>.csv "$D"/
    sudo find "$D" -type f -exec sha256sum {} + | sudo tee "$D.sha256"
    
  2. Confirm version and exposure. Read the Plex version in App Center > My Apps, then test port 32400 from outside the client's network; this covers that port only, so also read Plex Web > Settings > Remote Access. Pass: version 1.43.3 or later, nmap shows 32400 filtered or closed, and curl prints 000 twice.

    nmap -Pn -p 32400 <client-public-ip>
    for U in https://<client-public-ip>:32400/ http://<client-public-ip>:32400/; do curl -sk -m 5 -o /dev/null -w "%{http_code} $U\n" "$U"; done
    
  3. Look for QNAP's indicators on the box. In Resource Monitor, look for processes named myawesomeproxy, mylovelyminer or x12345 and high CPU while nothing plays (running processes only), then run a Malware Remover scan. Pass: none of those names appears and Malware Remover reports no MR2104 detection.

  4. Check Plex's transcoder setting. The CVE-2026-96656 record says the TranscoderH264Options preference is passed on verbatim, and QNAP says to review transcoder options nobody set. Pass: the grep prints nothing.

    sudo grep -iE 'TranscoderH264Options="[^"]+"' "/mnt/plexdata/Plex Media Server/Preferences.xml"
    # Also list Codecs for the case file; QNAP says to empty it if Plex was exposed
    sudo find "/mnt/plexdata/Plex Media Server/Codecs" -type f \( -name '*.so' -o -name '*.dll' \) -exec ls -l {} +
    
  5. Search network logs for the attackers' domain. Search the client's exported DNS-resolver and firewall logs, from the oldest retained, for proxystream.st, the domain QNAP's FAQ names. Pass: no output; any hit means contact with known attacker infrastructure: treat it as a likely compromise and escalate.

    zgrep -iE 'proxystream\.st' /path/to/<client>-dns-and-firewall-exports/*
    

How do I fix Plex2Shell on a client's QNAP NAS?

Close the door first, then clear footholds, then rotate passwords, following QNAP's FAQ.

  1. Preserve evidence. Keep the check 1 folder and its hash file on the workstation, off the NAS, before any change, because the reinstall wipes the Plex folders. Pass: every line of the check below ends in OK.

    sha256sum -c "$D.sha256"
    
  2. Close the door. Click App Center > My Apps > Plex Media Server > Update, turn off Remote Access in Plex Web, remove the 32400 forward and UPnP, and drop any myQNAPcloud auto router rule for Plex. Pass: rerun check 2; it passes.

  3. Remove footholds. If Plex was ever internet-reachable on 1.43.2 or earlier, or checks 3 to 5 hit, remove Plex in App Center, do the clean QTS or QuTS hero reinstall QNAP advises, empty Codecs, reinstall Plex Media Server 1.43.3.10861 or later, and open a case at service.qnap.com with the evidence folder. Pass: the command below prints nothing.

    # Remount with the check 1 mount command after the reinstall
    sudo find "/mnt/plexdata/Plex Media Server/Codecs" -type f ! -newermt <reinstall-date> -exec ls -l {} +
    
  4. Rotate credentials. Sign out all devices in Plex account settings, then change the Plex password; change NAS admin and user passwords, rotate backup and cloud keys stored on the NAS, and enforce 2-step verification at Control Panel > System > Security > 2-step Verification (QNAP docs; users must finish setup at next login). Pass: the old NAS admin password fails and that page shows each administrator as Enabled.

  5. Rerun the checks. Pass: checks 2 to 5 all pass on the rebuilt box.

Where KinoSec fits

KinoSec's autonomous external network pentest checks whether each client's internet-facing IP ranges expose a service on port 32400, such as a Plex Media Server forwarded from a QNAP box, and reports it with remediation steps. The router forward or UPnP rule that exposes Plex lives outside the NAS, so it can outlast the person who set it up. A pentest run with your client's permission and scope finds what actually answers from the internet, tests whether known weaknesses in it really work, and puts the result in a report you hand to that client. It tests from the outside only; checks 3 to 5 cover what is inside the NAS.

Frequently Asked Questions

Does Plex2Shell affect Plex on Synology, Windows or Docker, not just QNAP?

Yes. The CVE-2026-96656 record lists Plex Media Server before 1.43.3.10861 as affected without naming a platform. QNAP's notice speaks only for QNAP boxes, where QTS and QuTS hero are not affected themselves. A client host running an older Plex Media Server on another platform needs the same update and exposure check.

How do I check if my clients' QNAP NAS was hit by Plex2Shell?

First, read the version in App Center > My Apps and test exposure with nmap -Pn -p 32400 <client-public-ip>. Second, look in Resource Monitor for myawesomeproxy, mylovelyminer or x12345 and run Malware Remover, per QNAP's FAQ. Third, search exported DNS and firewall logs with zgrep -i 'proxystream\.st' <exported-logs>; a hit means contact with known attacker infrastructure: treat it as a likely compromise and escalate.

What if a client still needs to stream Plex from outside the office?

QNAP's advice is to reach Plex through a VPN, such as QNAP's QVPN Service, instead of Plex Remote Access or a port 32400 forward, per QNAP's FAQ. Turn off Remote Access in Plex Web, remove the forward and UPnP, then run nmap -Pn -p 32400 <client-public-ip> from outside. It should show the port filtered or closed.

Should clients run apps like Plex on a business NAS at all?

That's a policy call for each client. QNAP's own hardening list sets the bar for any app on the box: keep QTS or QuTS hero and installed apps updated, schedule Malware Remover scans, turn on QuFirewall and use a VPN for remote access, per QNAP's FAQ. If a client keeps Plex, add it to the same patch routine as the NAS firmware.