Cisco Expressway root RCE
Cisco Expressway CVE-2026-76466: Public Root RCE Exploit (Hunt Only)
- Published
- 12 November 2026
- Added
- 13 November 2026, 11:25 UK
- Last updated
- 13 November 2026
Nothing to block1 to hunt2 behaviours to hunt
Hunt3 platforms
Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.
- Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
- SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
- Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral
These queries can return false positives. Know your environment and confirm a hit before acting.
Summary
A public exploit gives root on clustered Cisco Expressway nodes through hard-coded Erlang credentials on TCP 4372. On 12 November researcher Nicolas Krassas (dinosn) published a working exploit and fleet detector on GitHub.
Do now
- Run the hunt.
- Patch CVE-2026-76466 now.
- Check for the listed behaviours.
Indicators 1
| Value | Type | Action | Copy |
|---|---|---|---|
CVE-2026-76466 | Other | monitor |
Sources Cisco · github.com · GBHackers · Cal-CSIC
More detail
What to do
- Upgrade clustered Expressway-C and Expressway-E nodes on X15.5.3 or earlier to X15.5.20, and migrate X14 and earlier to a fixed release; Cisco lists no workaround.
- Until then, allow TCP 4371 and 4372 to each node only from its configured cluster peers, at the perimeter and on internal firewalls, and confirm from a non-peer network that the ports are closed.
- Fill the cluster peer placeholders in the hunts with your Expressway peer addresses and run them over traffic since 12 November 2026.
- Treat a non-peer connection to TCP 4372 on an affected node as a possible root compromise: collect a diagnostic snapshot, check for new admin accounts, configuration changes and unexpected outbound connections from the node, and rebuild from a fixed release if in doubt.
- Where clustering is not needed, run Expressway as a standalone node; Cisco ties the flaw to clustered deployments.
Behaviours to hunt 2
Behaviours are leads, not confirmed indicators, and can match legitimate activity. Compare any hit against your own baseline and environment before acting.
alert Non-peer connection to Expressway cluster port 4371 or 4372
Look forConnections to TCP 4371 or 4372 on a Cisco Expressway node from any address that is not one of its configured cluster peers
Why it mattersThe CVE-2026-76466 exploit reaches the Erlang cluster database service on TCP 4372 and authenticates with a hard-coded node name and cookie, then runs commands as root. Only cluster peers should ever connect on 4371 or 4372. Tuning: replace the documentation peer addresses 192[.]0[.]2[.]10 and 192[.]0[.]2[.]11 with your peers; in Defender XDR any managed device connecting out to these ports is unexpected, because Expressway nodes and their peers do not run Defender for Endpoint. Expected false positives: a newly added cluster peer before the allowlist is updated, and authorised vulnerability scans. Cisco
Log sourceFirewall, NetFlow or load-balancer logs in front of Expressway (Splunk Network_Traffic, Google SecOps NETWORK_CONNECTION); Defender XDR DeviceNetworkEvents for managed devices that connect out to those ports
QueriesKQL · SPL · YARA-L
alert CVE-2026-76466 exploit script or wombat node name
Look forThe public CVE-2026-76466 exploit run from a managed host: a command line naming cve_2026_76466 or the Erlang node wombat@127[.]0[.]0[.]1
Why it mattersdinosn's exploit ships as exploit/cve_2026_76466.py with probe, ping and uid modes and hard-codes the node name wombat@127[.]0[.]0[.]1. Running it from inside the network means someone is testing or attacking Expressway nodes. Tuning: the script name and node name are specific; no broad tool names are matched. Expected false positives: your own authorised scans with the detector; confirm with the team that ran them. github.com
Log sourceDefender XDR DeviceProcessEvents; Sysmon event 1 or Linux process auditing in Splunk or Google SecOps
QueriesKQL · SPL · YARA-L
Affected countries and sectors
- Targets
- Global
- Sectors
- Not stated
Background
Cisco fixed CVE-2026-76466 (CVSS 9.8) on 21 October 2026: clustered Cisco Expressway-C and Expressway-E nodes, virtual and appliance, on X15.5.3 and earlier (and X14 and earlier) let an unauthenticated attacker run operating-system commands as root through the cluster database service. On 12 November researcher Nicolas Krassas (dinosn) published a working exploit and fleet detector on GitHub. It opens TLS to TCP 4372, completes the Erlang distribution handshake as the hard-coded maintenance node wombat@127[.]0[.]0[.]1 with the hard-coded cookie that is the same on every affected install, and calls os:cmd as root; it was tested on Expressway-C X15.3.2 in the factory-default TLS Permissive mode. Cisco says there is no workaround and, at the time of its advisory, knew of no malicious use; no exploitation has been reported since the code went public. No attacker infrastructure exists yet, so this entry is hunt and alert only. Its hunts flag connections to TCP 4371 or 4372 from anything that is not a cluster peer, and the public exploit being run from a managed host.