On October 20, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added six vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, indicating reliable evidence of active exploitation in the wild. This action, under Binding Operational Directive (BOD) 22-01, mandates that Federal Civilian Executive Branch (FCEB) agencies remediate these flaws by specified deadlines. The most prominent additions are four vulnerabilities in Plex Media Server, dubbed "Plex2Shell," which can be chained to achieve unauthenticated remote code execution. The other two flaws affect Siemens Software Center and EG Secure Solutions SiteGuard Server Edition. CISA strongly urges all organizations to prioritize patching these vulnerabilities to defend against active threats.
The six vulnerabilities added to the KEV catalog are:
Plex2Shell Attack Chain: A series of four vulnerabilities in Plex Media Server that, when chained, allow unauthenticated RCE. Attackers are reportedly using this chain to deploy cryptocurrency miners and proxy malware.
Siemens Software Center Vulnerability:
EG Secure Solutions Vulnerability:
1.43.3.10861 (patched on August 3, 2026).Exploitation of these vulnerabilities can lead to severe consequences:
The inclusion in the KEV catalog confirms that these are not theoretical risks; threat actors are actively weaponizing them. Organizations that have not patched are at a high and immediate risk of compromise.
Under BOD 22-01, federal agencies have strict deadlines:
CVE-2026-106931 (EG Secure), CVE-2026-96652 (Plex), and CVE-2026-96654 (Plex).CVE-2026-96655 (Plex), CVE-2026-96656 (Plex), and CVE-2026-110936 (Siemens).CISA recommends all organizations adopt a similar risk-based prioritization schedule. Internet-facing systems, such as Plex Media Servers and SiteGuard appliances, should be treated as the highest priority.
The following patterns may help identify vulnerable or compromised systems:
/photo/:/transcode?url=Plex Media Server.execmd.exe, powershell.exe, or cryptominer executables.C:\Program Files (x86)\Siemens\Software Center\Plex Media Server LogsPlex Media Server process for outbound network connections to unexpected destinations or the creation of suspicious files and processes. For the Siemens flaw, use EDR to detect DLL sideloading by monitoring for processes loading DLLs from non-standard directories. Reference D3FEND technique Process Analysis.Network Traffic Analysis.1.43.3.10861 or later. Contact Siemens and EG Secure Solutions for their specific patch guidance. Reference D3FEND Hardening technique Software Update.Local File Permissions.Applying vendor patches is the most effective way to remediate all six vulnerabilities.
Mapped D3FEND Techniques:
Enable comprehensive logging on affected systems to detect exploitation attempts and post-compromise activity.
Restrict network access to internet-facing applications like Plex Media Server to only trusted IP ranges.
Mapped D3FEND Techniques:
The primary countermeasure is to adhere to a strict patch management cycle guided by threat intelligence like the CISA KEV catalog. For the Plex2Shell flaws, administrators must immediately update Plex Media Server to version 1.43.3.10861 or newer. Similarly, patches from Siemens and EG Secure Solutions must be deployed. Organizations should use asset management and vulnerability scanning tools to identify all affected instances and automate patch deployment where possible. The KEV designation signifies an active and present danger, elevating the urgency of these updates above routine patching. Verification scans should be conducted post-deployment to confirm successful remediation across the entire environment.
To detect exploitation of the Plex2Shell SSRF vulnerabilities (CVE-2026-96652, CVE-2026-96654, CVE-2026-96655), security teams should implement network traffic analysis focused on web server logs and netflow data. Specifically, monitor for inbound requests to Plex servers targeting the /photo/:/transcode endpoint where the url parameter contains unexpected values, such as localhost addresses (127.0.0.1), internal RFC1918 IP addresses, or URLs pointing to external, non-Plex domains. Furthermore, monitor for unusual outbound connections from the Plex server itself, as this could indicate a successful SSRF callback or post-compromise C2 communication. Baselining normal traffic patterns for the Plex server is essential to quickly identify these anomalous connections.
To counter the post-exploitation impact of attacks like Plex2Shell, which deploy unauthorized software like cryptocurrency miners, organizations should implement application control or executable allowlisting on servers. On a dedicated system like a Plex Media Server, the set of required executables is typically small and predictable. By creating a policy that only allows known, legitimate executables to run (e.g., Plex Media Server.exe and standard OS binaries), the execution of dropped malware would be blocked. This defense-in-depth measure is highly effective at preventing attackers from achieving their objectives even if they successfully exploit a vulnerability to gain initial code execution.
Plex patches the vulnerabilities that would later be known as the Plex2Shell chain in version 1.43.3.10861.
CISA adds six vulnerabilities, including the Plex2Shell flaws, to its KEV catalog.
Deadline for US federal agencies to patch CVE-2026-106931, CVE-2026-96652, and CVE-2026-96654.
Deadline for US federal agencies to patch CVE-2026-96655, CVE-2026-96656, and CVE-2026-110936.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.