Plex Media Server file write exploited via Plex2Shell chain for code execution
CVE-2026-96656 is the last link in the four-CVE Plex2Shell chain. Attackers use it to plant code in the Codecs folder, and exploitation began 2026-10-17. Upgrade to 1.43.3.10861 or later, then check for implants.
What you need to know
- Exposure: Plex Media Server on all platforms before 1.43.3.10861, including the early 1.43.3.10828 build. Censys counts roughly 30% of about 324,000 visible hosts as vulnerable.
- Impact: alone, the bug needs admin rights. Chained with three other Plex2Shell CVEs, it gives an unauthenticated remote attacker code execution as the Plex service account.
- Exploitation: seen in the wild since 2026-10-17, dropping cryptominers and proxyware. CISA added it to KEV on 2026-10-20 with a 2026-10-23 due date.
- Fix: upgrade to 1.43.3.10861 or later. Linux, NAS and Docker installs need a manual update. Upgrading does not remove implants already planted.
- Detect: look for unfamiliar .so/.dll files in the Codecs folder, transcoder options you did not set in Preferences.xml, and Plex child processes such as mylovelyminer.
What's happening
CVE-2026-96656 is an external control of file path flaw (CWE-73) in Plex Media Server. An admin-level user can use it to write arbitrary files into the transcoder Codecs directory, where they are later executed 1,3. It scores 7.2 because it requires admin privileges 3. It is the final stage of Plex2Shell, a four-CVE chain found by researcher Zach Main 3,5. The other three are CVE-2026-96652 (SSRF), CVE-2026-96654 (access to internal agent functions over loopback) and CVE-2026-96655 (admin token disclosure) 1. Plex says the chain gives an unauthenticated remote attacker code execution with the privileges of the Plex Media Server process 1. The researcher scores the full chain 9.8 5.
All platforms running builds before 1.43.3.10861 are affected 1,3. Plex's original 2026-09-01 notice described the affected range as 1.43.2 and earlier. Early 1.43.3 builds such as 1.43.3.10828 are also vulnerable, and Censys counts nearly 8,000 hosts on that build 6. Censys sees about 324,000 Plex Media Server hosts, about 44% of them in the US and mostly on residential networks 6. Roughly 30% run a vulnerable build 6. Under 2% of the vulnerable hosts upgraded in the first three days after the chain went public 6. Shadowserver had already reported more than 36,000 exposed, unpatched servers in early September 11.
This was not a zero-day. The fixed build shipped in early August 3,6, and Plex announced the update on 2026-09-01, about six weeks before attacks began 1. The researcher's write-up and PoC went public on 2026-10-16 5,6. On 2026-10-17, an independent honeypot operator recorded the first real exploitation. The traffic came from three source IPs, a fourth host served downloaded files, and the operator then saw an XMRig miner and a proxy tool named myawesomeproxy 7. SecurityWeek and The Hacker News report the same miner and proxy payloads 8,9. On 2026-10-19, Plex said the flaws are being actively and widely exploited, with compromised servers used for mining and for routing third-party traffic 1.
CISA added the CVE to KEV on 2026-10-20 and requires forensic triage 2. BleepingComputer reports that CISA warns all four chain CVEs are exploited 10. No source attributes the activity to a named threat actor, and KEV lists ransomware use as unknown 2. The only public first-hand telemetry is a single honeypot, so its view of the campaign may be partial 7.
How it works
The flaw sits in the H.264 transcoder options preference (TranscoderH264Options). The server appends that value, unchanged, to the x264 encoder options on every transcode 3. An admin can abuse this to make the server write arbitrary files into the Codecs directory 1,3. Code execution depends on a second weakness. Plex loads .so files at transcoder startup with no signature, execute-bit or symbol check, so a planted file runs the next time it is loaded 3,6.
Used alone, the bug requires owner or admin privileges. It is reachable over the network and needs no user interaction 3. In the Plex2Shell chain, the three earlier CVEs supply that admin access. Any internet-reachable server on an unpatched build is therefore exposed to unauthenticated attackers 6. Plex warns that internet-reachable servers on builds older than 1.43.3.10861 may already be compromised 1. Plex recommends against directly forwarding port 32400 1.
Patching closes the chain, but Censys notes it leaves any implant already planted in the Codecs directory in place and does not invalidate an admin token that was already leaked 6. Servers that were exposed on a vulnerable build since 2026-10-16 still need checking after the upgrade 1,6.
What to do
In order of priority- 1
Upgrade Plex Media Server to
1.43.3.10861or newer 1,3. Windows and macOS servers update automatically only if automatic updates are enabled. Linux, NAS and Docker installs must be updated manually 1,6. - 2
US federal agencies must meet the KEV due date of 2026-10-23. That means applying vendor mitigations in line with BOD 26-04 and the Forensics Triage Requirements, or discontinuing the product if mitigations are unavailable 2.
- 3
Turn off Remote Access (Settings > Remote Access) where it is not needed 1. Avoid forwarding port
32400directly to the internet 1. - 4
Plex says to assume an internet-reachable server on a build older than 1.43.3.10861 may be compromised 1. Upgrading does not remove implants or revoke exposed tokens 6. If compromise is found or cannot be ruled out, rebuild from a clean install rather than reusing the old data directory 1.
- 5
If you cannot rebuild immediately, take these minimum steps from Plex 1: - Delete everything in the Codecs folder. - Check
Preferences.xmlfor transcoder options you did not set. - Sign out all devices. - Change the Plex account password. - 6
Consider every resource the Plex service account had access to as exposed, such as network shares mounted on the host and secrets kept on the same machine or VM 1. Rotate those credentials and review access to those shares.
Detection
- Inventory versions under Settings > General in Plex Web. Any build below
1.43.3.10861is vulnerable 1. A bare "1.43.3" is not sufficient, because1.43.3.10828is still affected 6. - Check the Plex Codecs folder for unfamiliar
.soor.dllfiles 1. Plex published no specific filenames, so defenders will need to baseline the folder themselves, for example against a clean install of the same build. - Review
Preferences.xmlfor transcoder options you did not set 1. Pay particular attention to the H.264 transcoder options value, which is the injection point 3. - Hunt in EDR or process telemetry for unrecognized children of Plex Media Server, such as
myawesomeproxy,mylovelyminerorx123451. Also flag sustained high CPU while nothing is playing 1. - Search DNS, proxy and firewall logs for
proxystream.st1. The Hacker News reports the subdomainota.proxystream.stas the miner's mining server 9. Add the honeypot IPs and hashes as lower-fidelity indicators, since they reflect one sensor only 7. - Find hosts exposing TCP
32400to the internet, including NAS devices and Docker hosts 1. Network owners can check Shadowserver's daily unpatched-Plex reports, issued since 2026-09-04 11. - The honeypot operator published pcaps for signature work and links to a detection folder in the researcher's Plex2Shell GitHub repository 7. VulnDigest has not reviewed either, so validate them before use.
Indicators
As published by the cited sources| Type | Value | Context |
|---|---|---|
| file path | Unfamiliar .so/.dll files in the Plex Codecs directory | Vendor-published indicator; no specific filenames given.1 |
| other | Child processes of Plex Media Server named myawesomeproxy, mylovelyminer, x12345 | Vendor-published process names seen on compromised servers.1 |
| domain | proxystream.st | Vendor flags outbound connections; The Hacker News names ota.proxystream.st as the mining server.1 |
| ip | 217.60.194.116 | Download source for files 'docker' and 'x' (honeypot).7 |
| ip | 45.194.92.222 | Exploitation source against honeypot; first seen.7 |
| ip | 91.92.40.202 | Exploitation source against honeypot.7 |
| ip | 176.65.139.228 | Exploitation source against honeypot.7 |
| sha256 | 5712ef510481f15fe8b18fdd10b73026d57cb3d9d151878a692358b99a464441 | File named 'docker', downloaded from 217.60.194.116.7 |
| sha256 | 68938fb428f2bcfef4ede62f7b29cd0f15f37ed59e94462c099f2ca64e36baa7 | File 'x' downloaded from 217.60.194.116 (UPX-packed).7 |
| sha256 | b20f39fc00d242e706b6c30367ad811c676e0575050a4ec2f30104b696944b49 | File 'x' (UPX-unpacked).7 |
| sha256 | e546b10aee5edc754da4f9b0baace00392257121911f630145078eafad1e6bd9 | 'myawesomeproxy' proxy binary seen running on the honeypot.7 |
| sha256 | 2d3c618b21a7e2f8bcd735da188e44a7609ff3f204832dd0781cd09e4388c9db | XMRig miner seen on the honeypot after exploitation.7 |
Timeline
Plex Media Server 1.43.3.10828 released; Censys later reports this early 1.43.3 build is still vulnerable. 4
Zach Main reports the Plex2Shell chain to Plex. 5
Plex acknowledges the report and pays a bounty. 5
Fixed build 1.43.3.10861 released, per Censys (CISA's CSAF advisory lists 2026-08-03). 6
Plex announces the security update, without CVE IDs, and urges owners to update. 1
CVEs published; CISA issues CSAF advisory VA-26-266-01. 3
Researcher publishes the technical write-up and PoC. 6
First in-the-wild exploitation seen on a honeypot; miner and proxy payloads dropped. 7
Plex updates its notice with CVE details and confirms active, widespread exploitation. 1
CISA adds CVE-2026-96656 to KEV with forensic triage required. 2
KEV remediation due date for US federal agencies. 2
Sources
- 1Important Security Update for Plex Media Server v1.43.2 and earlierPlex · Vendor · Oct 19, 2026
- 2CISA KEV entry for CVE-2026-96656CISA · Government · Oct 20, 2026
- 3CISA CSAF VA-26-266-01 Plex Media ServerCISA · Government · Sep 23, 2026
- 4Plex Media Server release announcement (1.43.3.10828)Plex · Vendor · Jul 14, 2026
- 5Plex2ShellZach Main (zmain.info) · Research · Oct 16, 2026
- 6October 20 Advisory: Plex Media Server Remote Code Execution ChainCensys · Research · Oct 20, 2026
- 7Plex vulnerabilities being exploited in the wild to drop a cryptominerboredhackerblog (independent researcher) · Research · Oct 17, 2026
- 8Plex2Shell Exploit Chain Weaponized Against Plex Servers Hours After DisclosureSecurityWeek · News · Oct 19, 2026
- 9Hackers Exploit Plex2Shell Flaws to Install Crypto Miners and Linux Proxy BackdoorThe Hacker News · News · Oct 19, 2026
- 10CISA: Hackers chain Plex flaws in Plex2Shell attacks to breach serversBleepingComputer · News · Oct 21, 2026
- 11Over 36,000 exposed Plex servers vulnerable to recent flawsBleepingComputer · News · Sep 9, 2026
Confirmed by vendor and government. Researched and drafted by the VulnDigest briefs agent from 11 sources, then checked against them by a separate review step on Oct 23, 2026.
Plex confirms active, widespread exploitation, but the only public first-hand telemetry comes from one independent honeypot. The IPs and hashes listed reflect that single sensor and may be incomplete.
Severity HIGH reflects this CVE's own 7.2 score, which requires admin rights. Chained with the other three Plex2Shell CVEs, it allows unauthenticated code execution; the researcher scores the full chain 9.8.
Builds labelled 1.43.3 are not automatically safe. Only 1.43.3.10861 and later are fixed; early builds such as 1.43.3.10828 remain vulnerable.
Sources differ by one day on when the fixed build shipped: 2026-08-04 per Censys, 2026-08-03 per CISA's CSAF advisory.
No threat actor has been attributed, and CISA lists ransomware use as unknown.
Spotted an error? Open an issue on sochub.io.