Cisco Expressway CVE-2026-76466 (CVSS 9.8) Exploited and in CISA KEV: Hard-Coded Cluster Cookie Gives Unauthenticated Root, Attackers Pivoted to Internal Nodes — Upgrade to X15.5.20 by 23 November

Critical · 2026-11-21 · By H.A

Cisco Expressway CVE-2026-76466 (CVSS 9.8) Exploited and in CISA KEV: Hard-Coded Cluster Cookie Gives Unauthenticated Root, Attackers Pivoted to Internal Nodes — Upgrade to X15.5.20 by 23 November

A hard-coded cluster credential in clustered Cisco Expressway nodes is being exploited for unauthenticated root access after a public PoC, and CISA has added CVE-2026-76466 to KEV with a 23 November deadline and forensic triage required.

Overview

A critical flaw in clustered Cisco Expressway deployments is now being used in real attacks. Tracked as CVE-2026-76466 (CVSS 3.1 score 9.8, CWE-798), it lets an unauthenticated remote attacker run operating-system commands as root on Expressway-C (Core) and Expressway-E (Edge) nodes, on both virtual machines and appliances. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on 20 November 2026. US federal civilian agencies have until 23 November 2026 to act, and CISA has flagged the entry for forensic triage, which means agencies are expected to look for signs of compromise, not just patch.

The first confirmed intrusion followed a public proof-of-concept that appeared on GitHub about two weeks after Cisco's fix. Researchers investigating the case say the attackers broke into two internet-facing Expressway nodes and then used the cluster's own trust relationships to take over two more nodes inside the victim's internal network.

Expressway is the gateway many organisations use to connect Webex, Unified CM, remote and mobile workers, and outside video partners to internal collaboration systems. An Expressway-E node normally sits in the DMZ with one leg facing the internet, so a root-level compromise there is a direct route inside.

The Vulnerability

According to Cisco's advisory (cisco-sa-vcs-static-cred-hr7EWZ8t, bug ID CSCww27732), the flaw is in the Expressway database service that cluster peers use to synchronise with each other. Cisco gives two causes:

An attacker who holds the cookie and can reach the service can connect to it and call specific remote procedure call (RPC) commands that run arbitrary commands as root.

The public proof-of-concept says the service is the Erlang distribution listener on TCP 4372 (over TLS), and that a vendor maintenance identity and its matching cookie are hard-coded in the cluster-manager module, identical on every affected install. The author says they tested only Expressway-C X15.3.2 in a two-node cluster in "Permissive" mode, and did not test Enforcing mode, Expressway-E or X14. The advisory and the PoC describe the affected TLS mode differently, so do not treat any TLS setting as a safe configuration.

Key facts from the vendor:

Timeline

Tradecraft

The responders describe a short path from edge to core:

No one has attributed the attack to a named threat actor, and the victim has not been identified. Cisco has not published information on any further victims.

Indicators of Compromise

The researchers published these indicators (defanged):

No file hashes have been published.

Detection

grep -n "nodeup" erlang.log* | grep -i "wombat"
find /mnt/harddisk -maxdepth 2 -name "*.py" -newermt "2026-11-01" -ls

Recommended Actions

Analyst Assessment

The pattern is familiar: a hard-coded secret in an edge appliance, a fix with no workaround, and exploitation within days of a public PoC. Two details stand out here. First, the clustering requirement narrows the attack surface, but larger organisations, the most valuable targets, are the ones most likely to run Expressway in clusters. Second, cluster trust turns one exposed edge node into a bridge to internal nodes that were never reachable from the internet. Defenders who patch only the DMZ boxes and ignore the internal Expressway-C peers may leave attackers with a foothold.

The AI-assisted Python tooling fits a wider trend this month of attackers quickly building custom post-exploitation scripts. We expect more scanning for TCP 4372 now that the flaw is in KEV. Any organisation with clustered Expressway nodes still below X15.5.20 should assume it is being targeted and should hunt as well as patch.

Sources

REEF SENTINEL