What landed in CVE-land this week

This week's headline is a four-CVE chain against Plex Media Server that CISA added to the Known Exploited Vulnerabilities catalog on 2026-10-20. All four are confirmed exploited in the wild; together they turn an admin session (or a leaked token) into reliable remote code execution on the host. Under BOD 26-04, federal civilian agencies must remediate KEV entries on the schedule CISA sets. The same prioritization logic applies to everyone else: these are not theoretical.

This digest covers the Plex chain in depth because the mechanics matter, then closes with a Cisco advisory published 2026-10-26 that application-security teams should not ignore.

Lead: the Plex Media Server chain (CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, CVE-2026-96656)

CISA's catalog entries describe four distinct primitives that chain cleanly. In isolation, each is awkward. Combined, they carry an attacker from "I have an X-Plex-Token" to "I own the Plex process."

Here is what each primitive does, mapped to its role in the chain:

Read the four CISA entries together and the chain writes itself. CVE-2026-96652 carries an attacker's request across the trust boundary. CVE-2026-96655 reaches internal plugin interfaces via the transcode path. CVE-2026-96654 invokes functions with attacker-controlled parameters. CVE-2026-96656 drops a payload where load-time execution occurs. CISA's listing names each step as chainable with the other three.

What should defenders do?

  1. Treat any internet-exposed Plex Media Server as presumed compromised until patched and the host is inspected. The KEV listing confirms in-the-wild exploitation, not speculation.
  2. Audit X-Plex-Token issuance, revoke tokens, and rotate credentials for any account that touched the host.
  3. Copy the Plex plugin directory from the host and diff it against a known-good source. Arbitrary file write that executes on load is detectable: unexpected files, odd timestamps, or non-vendor hashes in plugin paths are high-signal indicators.
  4. Review egress. The CVE-2026-96652 SSRF forces outbound POSTs. If your Plex host has been reaching URLs that are not Plex-owned CDNs, metadata APIs, or your own update infrastructure, treat that as an incident.

A minimal detection sketch for a host filesystem check, assuming Plex's default plugin layout on a Linux deployment:

# Enumerate files under the Plex plug-in support tree modified in the last 30 days,
# excluding vendor-signed update artifacts. Review anything surprising.
PLEX_ROOT="/var/lib/plexmediaserver/Library/Application Support/Plex Media Server"
find "$PLEX_ROOT/Plug-ins" "$PLEX_ROOT/Plug-in Support" \
     -type f -mtime -30 \
     \( -name '*.py' -o -name '*.pyc' -o -name '*.so' -o -name '*.sh' \) \
     -printf '%T@ %p\n' | sort -nr | head -50

# Pair that with egress review: any outbound POST from the Plex host to
# non-Plex destinations is suspicious given the SSRF primitive.
journalctl -u plexmediaserver --since "30 days ago" | grep -Ei 'protocol=|transcode/universal'

Treat the output as triage, not confirmation. The goal is to lower the bar for noticing the two most externally visible pieces of this chain.

Two more items landed on KEV the same day: CVE-2026-110936 in Siemens Software Center (uncontrolled search path element, local DLL hijack to code execution) and CVE-2026-106931 in EG Secure Solutions SiteGuard Server Edition (OS command injection to root or SYSTEM). Both are actively exploited; the latter warrants priority because the vendor is a security product and the end state is OS-level command execution with full privilege.

Second finding: Cisco Expressway Series RCE (CVE-2026-76466)

Published 2026-10-26, not yet listed as exploited in the wild. Cisco's advisory describes a critical flaw in the database service feature of Cisco Expressway Series that allows an unauthenticated remote attacker with network access to execute arbitrary OS commands as root. Two conditions enable the attack: the use of persistent cookies, and insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering. Despite that mode's name, client certificates are not actually validated on affected versions. An attacker with the relevant cookies can exploit the flaw by connecting to the database service.

For blue teams, three actions:

A vulnerability absent from the KEV catalog is still a real vulnerability. CVE-2026-76466 sits at the network edge of enterprise collaboration deployments, a position that rewards speed over perfect inventory.

Patch the Plex chain this week. Patch Expressway on the regular critical cadence. When you do, verify the fix on the host, not just in your ticketing system.

Verifiable security.