Security Digest · Nov 20, 2026 · Vulnerability · Network edge
Cisco Expressway CVE-2026-76466: Cluster Root RCE Exploited
Clustered Cisco Expressway X15.5.3 and earlier lets attackers run commands as root. Exploited after a public PoC, now in CISA KEV. Upgrade to X15.5.20.
Our verdict
Act now
If any of your Expressway nodes are clustered and below X15.5.20, upgrade now and fence off the cluster ports: the credential that guards root access is the same on every install, a public exploit exists, and CISA lists the flaw as exploited.
Who must act: Organizations running clustered Cisco Expressway-C or Expressway-E nodes, virtual or appliance, on X15.5.3 or earlier or on any X14 or older release, starting with internet-facing Expressway-E clusters.
Who can relax: Teams that run no Expressway, those already on X15.5.20, and those with a single unclustered node, which Cisco says is not affected, though X15.5.20 also fixes eight other Expressway CVEs.
- Affected
- Cisco Expressway-C and Expressway-E, virtual and appliance, configured in a cluster
X15.5.3 and earlier X15 releases
X14 and earlier (the CVE record lists X8.1 through X14.3.7); no fix on these trains - Fixed in
- Cisco Expressway X15.5.20
- CVSS
- 9.8 (v3.1, vendor)
- EPSS
- 2.2% (percentile 83)
- CISA KEV
- Yes, listed as known exploited
- Exploitation
- Exploited in the wild
- Severity
- Critical
What to do
- List every Expressway-C and Expressway-E node, note which belong to a cluster, and record the release each one runs.
- Upgrade clustered nodes on X15.5.3 or earlier to X15.5.20; nodes on X14 or earlier have no fix on their train and must migrate to X15.5.20.
- Until every peer is upgraded, block TCP 4371-4372 at the firewall except between trusted cluster peers, as F6 recommends, starting with internet-facing Expressway-E nodes.
- Before upgrading, preserve system logs from every node, including erlang.log, so you can investigate afterwards.
- If you find signs of compromise, treat every node in the cluster as compromised: rebuild it, rotate the credentials and certificates it holds, and hunt for lateral movement from Expressway addresses.
How to check if you are affected or compromised
- Search erlang.log on each node for nodeup entries naming an unexpected Erlang node, such as the hard-coded wombat@ maintenance identity used by the public exploit; F6 calls this a key sign of exploitation.
- Check firewall and flow logs for connections to TCP 4371-4372 from anything other than cluster peers, and for the F6-published addresses 66.179.31[.]32 and 18.130.47[.]116.
- Look for unexpected Python scripts on the node matching F6's path pattern /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py.
- Review internal logs for network scanning, SMB, SQL Server, WinRM or GitLab access that originates from Expressway addresses.
What happened#
On November 20, 2026, CISA added CVE-2026-76466 to its Known Exploited Vulnerabilities catalog, based on evidence of active exploitation. The flaw is in Cisco Expressway, the gateway that lets remote staff, partners and guests reach an organization's Cisco calling, video and messaging services. Cisco's advisory, published October 21, rates it 9.8. It says an unauthenticated, remote attacker with network access can run operating system commands as root through the cluster database service. The KEV entry gives federal agencies until November 23.
Cisco attributes the bug to "the use of persistent cookies" plus missing client certificate validation when TLS Verify Mode is enabled for clustering. An attacker "with possession of the cookies" can connect to the database service and call specific RPC commands. Cisco classes it as CWE-798, use of hard-coded credentials, and credits Stefan Aleksic of Jane Street. A public proof of concept, posted on GitHub on November 5, explains the "possession" part. Its author writes that the cluster manager admits a hard-coded maintenance node identity, prefixed wombat@, together with a matching hard-coded Erlang cookie. Both are compiled into the product, so every affected install shares them.
According to the security firm F6, as reported by SecurityWeek, attackers used the flaw against a Russian organization soon after the exploit appeared. They first took over two internet-facing Expressway nodes running X15.5.3, then pivoted to two cluster peers on the internal network. With root, they staged Python tools to scan the network, find SMB shares, talk to SQL Server and WinRM, and search GitLab repositories for credentials. F6 says comments in the code suggest an AI assistant helped the attackers adjust the scripts during the attack. It did not name the victim or attribute the attack to a known group.
Who is affected#
Cisco says the flaw affects Expressway-C and Expressway-E, virtual and appliance, only when the devices are configured in a cluster. X15.5.3 and earlier X15 releases are fixed in X15.5.20. For X14 and earlier, Cisco's only guidance is to "migrate to a fixed release". The CVE record lists affected versions back to X8.1. Cisco lists no workarounds. X15.5.20 also ships Cisco's October hardening release, which fixes eight more Expressway CVEs (CVE-2026-76490 through -76497, scored up to 8.6). Cisco found those internally and says none are known to be exploited.
Do you really need to act?#
Yes, if you run an Expressway cluster. The stated precondition, holding the cookie, is not a real barrier when the cookie is the same on every device. CISA's scoring in the CVE record marks the flaw as automatable with total technical impact. Expressway-E nodes are built to sit at the network edge, and the F6 case shows what follows: root on an edge node, then the internal cluster peers, then the rest of the network.
Two caveats. Cisco's advisory, still at version 1.0 when we checked on November 21, says Cisco is not aware of malicious use, while CISA and F6 say it has happened. Second, do not count on TLS settings as a defense. The proof of concept's author reports a working exploit against a two-node X15.3.2 cluster in TLS Permissive mode and did not test Enforcing mode. Cisco offers no configuration workaround. How many Expressway clusters are reachable from the internet is not disclosed as of Nov 21, 2026.
What to do now#
- Inventory every Expressway-C and Expressway-E node, mark which are clustered, and record each node's release.
- Upgrade clustered nodes on X15.5.3 or earlier to X15.5.20. Nodes on X14 or earlier have no fix on their train and must move to X15.5.20.
- Until every peer is upgraded, follow F6's advice: allow TCP 4371 and 4372 only between trusted cluster peers. Confirm from outside your network that those ports are closed, for example with
nmap -Pn -p 4371,4372 <expressway-public-ip>. - Before upgrading, preserve logs from every node, including
erlang.log. - If you find evidence of compromise, treat the whole cluster as compromised: rebuild the nodes, rotate the credentials and certificates they held, and hunt for lateral movement from Expressway addresses.
How to tell if you were hit#
F6 points to the Erlang system log. According to Techgenyz, which summarized F6's indicators, a nodeup entry in erlang.log naming the attacker's node is an important sign. In the public exploit, that node is the hard-coded wombat@ identity. A first pass is grep -i 'nodeup' erlang.log*, checking any node name that is not a known cluster peer. F6 also published two IP addresses, 66.179.31[.]32 and 18.130.47[.]116, and a file pattern for dropped scripts, /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py. A different attacker will use different infrastructure, so also review flow logs for connections to ports 4371-4372 from non-peers, and look for SMB, SQL Server, WinRM or GitLab traffic coming from Expressway addresses. Cisco has published no indicators of compromise as of Nov 21, 2026.
Timeline#
- — Cisco publishes the advisory (CVSS 3.1 9.8) and the October hardening release; X15.5.20 is the first fixed release.
- — A public proof of concept and detector appears on GitHub.
- — F6 reports the first known in-the-wild exploitation, against a Russian organization.
- — SecurityWeek reports F6's findings; Cisco's advisory still says it is unaware of malicious use.
- — CISA adds CVE-2026-76466 to KEV with a November 23 due date.
Vulnerability records
- CVE-2026-76466 · KEV 2026-11-20 · A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco…
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- Cisco — Cisco Expressway Series Remote Code Execution Vulnerability (cisco-sa-vcs-static-cred-hr7EWZ8t) sec.cloudapps.cisco.com
- CVE record — CVE-2026-76466 cve.org
- CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 20, 2026) cisa.gov
- CISA — Known Exploited Vulnerabilities catalog entry for CVE-2026-76466 cisa.gov
- Cisco — Cisco Expressway Series Security Hardening Release: October 2026 sec.cloudapps.cisco.com
- GitHub — dinosn/cve-2026-76466: public proof of concept and detector github.com
- Techgenyz — Cisco Expressway Vulnerability: Critical 9.8 Flaw Exploited techgenyz.com