Article
Plex2Shell: Four Plex Media Server CVEs Chained Into Remote Code Execution
Plex2Shell chains four Plex Media Server CVEs into remote code execution. CISA lists all four as exploited. See the fixed version and what to…
Quick links
Press Enter to search, Esc to close
Exploited vulnerability
An arbitrary file write flaw in Plex Media Server before build 1.43.3.10861.
In short
CVE-2026-96656 is an arbitrary file write flaw in Plex Media Server before build 1.43.3.10861. The CVE record says an admin user can write files that may be run when loaded, and that the TranscoderH264Options preference is appended verbatim to the option string of x264, the video encoder. CISA added it to its Known Exploited Vulnerabilities catalog on 20 October 2026 and marks it for forensic triage. In the researcher's chain it is the last step, the one that turns file write into code execution.
The CVE record says Plex Media Server before 1.43.3.10861 allows an admin user to write arbitrary files that may be executed on load. The preference TranscoderH264Options is appended verbatim to the option string of x264, the video encoder, on every transcode. At startup, all .so files are run without signature, execute bit or symbol checks.
On its own the flaw needs admin rights, and the score reflects that: the CVSS v3.1 vector sets privileges required to high. In the Plex2Shell chain an earlier step gives the attacker the owner's admin token, so an outsider reaches this step. The researcher says the result is code execution with the rights of the Plex process.
Plex says compromised servers were used to run cryptocurrency miners and proxy software. It lists unfamiliar .so or .dll files in the Plex Codecs folder as a sign of compromise.
Plex2Shell is the name for the chain of CVE-2026-96652, CVE-2026-96654, CVE-2026-96655 and CVE-2026-96656. CISA's entry for each one says it can be chained with the other three. Our Plex2Shell news post shows how the four steps fit together.
In our checks on 23 October 2026, a GitHub search for this CVE id returned 4 repositories, the earliest created on 17 October. By their descriptions they include the researcher's tool, a copy of it, a compromise checker and an incident write-up. We did not run or link any of them. Our dark web and chat monitoring found 4 Telegram posts naming this CVE between 17 and 21 October.
Plex Media Server before build 1.43.3.10861, according to the CVE record. Plex says 1.43.3.10861 and later are not affected.
Plex's post title says 1.43.2 and earlier, while its 19 October update gives the build number as the cutoff. Use the build number. The researcher's README names builds up to 1.43.3.10828 as vulnerable, so an early 1.43.3 build can still be affected.
Plex's update guide covers Windows, macOS, Linux, NAS devices and Docker. Plex says an internet-reachable server older than 1.43.3.10861 should be assumed possibly compromised.
Plex announces Plex Media Server 1.43.3 as a security release and says CVEs have been requested.
The CVE record is published, with CISA as the CVE numbering authority.
A public proof of concept is released, according to Plex.
Plex publishes the CVE details and says the flaws are being actively and widely exploited.
CISA adds the CVE to the Known Exploited Vulnerabilities catalog.
The CISA due date for US federal agencies. CISA marks this CVE as needing forensic triage.
Open Plex Web, go to Settings, then General, and read the version. Anything older than 1.43.3.10861 is affected. Compare all four numbers of the build, not only 1.43.3.
Install Plex Media Server 1.43.3.10861 or later. On a NAS the package manager may be behind, so Plex says to download the package from its Downloads page and install it by hand.
If you do not need remote access, turn it off under Settings, then Remote Access. Plex also advises against forwarding port 32400 directly unless you need it.
Delete nothing yet. First look in the Plex Codecs folder for .so or .dll files you did not expect, and check Preferences.xml for transcoder options you did not set. Plex also lists unknown processes started by Plex Media Server and sustained high CPU while nothing is playing.
Plex advises a clean installation instead of reusing the old data directory. Sign out of all devices in your Plex account, change the password, and treat anything the Plex service account could reach as exposed.
Plex says the flaws in this chain are being actively and widely exploited, and CISA added CVE-2026-96656 to its Known Exploited Vulnerabilities catalog on 20 October 2026. CISA lists use in ransomware campaigns as unknown.
Plex Media Server 1.43.3.10861 and later. Check Settings, then General, in Plex Web, and compare all four numbers of the build.
Plex advises turning off Remote Access if you do not need it and not forwarding port 32400 directly unless you need it. Updating is still required.
It lets an admin user write files that Plex Media Server later runs. The transcoder preference TranscoderH264Options is passed on unchecked, and shared object files are loaded without a signature check.
Not by itself, since it needs admin rights. In the Plex2Shell chain the earlier steps give the attacker the owner's admin token first.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.