Skip to content

Cisco Expressway root RCE CVE-2026-76466 reported exploited

Russian firm F6 reports the first in-the-wild exploitation of CVE-2026-76466, a CVSS 9.8 root RCE in clustered Cisco Expressway. Fixed in X15.5.20; a public PoC exists.

Published 3 min read

A critical Cisco Expressway flaw that Cisco patched a month ago is now reported exploited in the wild. CVE-2026-76466, CVSS 9.8, lets an unauthenticated remote attacker run arbitrary OS commands as root on a clustered Expressway. Cisco fixed it in X15.5.20 on October 21 (cisco-sa-vcs-static-cred-hr7EWZ8t). A public proof-of-concept is already out.

What's affected

The bug is in cluster deployments only. Per Cisco's advisory, it stems from network-database credentials associated with persistent cookies plus insufficient client-certificate validation on an RPC path when TLS Verify Mode is enabled for clustering. A standalone Expressway-C/E is not vulnerable to CVE-2026-76466 — but it still needs X15.5.20 for the hardening CVEs shipped in the same release.

  • Expressway Series X15.5.3 and earlier → fixed in X15.5.20
  • Expressway Series X14 and earlier → no fix; migrate to a supported release

Cisco states there are no workarounds.

Exploitation status

The exploitation claim comes from Russian cybersecurity firm F6, in a report relayed by The Hacker News. F6 says it observed the first in-the-wild exploitation of CVE-2026-76466, shortly after the public PoC appeared, against a Russian organization. The attackers first compromised two internet-facing Expressway devices, then pivoted to two additional cluster nodes on the internal network — four devices in total. F6 did not attribute the activity to a known threat actor.

Treat this as single-source for now: Cisco's advisory does not list the flaw as exploited and has not published indicators of compromise. The CVE, severity and fix, however, are confirmed by Cisco directly. The public PoC is published at github.com/dinosn/cve-2026-76466.

Action checklist

  1. Upgrade clustered Expressway-C/E to X15.5.20 now. If you run X14 or earlier, plan the migration immediately — there is no patch for that branch.
  2. Even for standalone deployments, move to X15.5.20 to pick up the companion hardening fixes.
  3. Where Expressway is internet-facing, treat it as a priority: a working PoC plus a CVSS 9.8 root RCE is the profile that gets mass-scanned within days.
  4. Hunt for anomalous root processes and lateral movement from Expressway nodes into the internal network, mirroring F6's described chain (edge device → internal cluster peers).
  5. If you cannot patch within the maintenance window, restrict management and clustering interfaces to trusted networks and review client-certificate validation settings.

Context

Expressway and its TelePresence VCS lineage sit at the network edge to broker video and mobile-and-remote-access traffic, which is exactly why a root RCE here is dangerous: the device already bridges the internet and the internal estate. The pattern in F6's report — compromise the exposed node, then walk into the cluster peers — is the standard edge-appliance kill chain. The practical takeaway does not depend on confirming F6's attribution: patch to X15.5.20, because a public PoC against a 9.8 is a short fuse.

Related stories