top of page

Cisco Expressway CVE-2026-76466 Is Being Exploited: F6 Found Root on Four Cluster Nodes. Upgrade to X15.5.20, Fence TCP 4371-4372, and Grep erlang.log for [email protected]

Writer: Patrick Duggan
Patrick Duggan
49 minutes ago
5 min read

If you run a clustered Cisco Expressway (C or E) on X15.5.3 or earlier, upgrade to X15.5.20 now. If you are on X14 or earlier, there is no fix on that train: you have to migrate to a fixed release. Until you can, allow TCP 4371 and 4372 only from your own cluster peers, and check every node's Erlang log for the line nodeup,'wombat@127.0.0.1'. A Russian incident response firm, F6, says attackers used this bug to get root on four Expressway nodes at one organization and then walked into its internal network.



What is confirmed


  • The bug. Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t, published Wednesday, October 21, 2026, rates CVE-2026-76466 9.8 (CWE-798, hard-coded credentials). Cisco says an unauthenticated remote attacker could "execute arbitrary operating system commands as root." The cause, in Cisco's words, is persistent cookies plus "insufficient validation of client certificates" in the cluster TLS setting, which lets an attacker who holds those cookies call RPC commands on the database service.

  • Who is affected. Expressway-C and Expressway-E, virtual and appliance, on a vulnerable release, configured in a cluster. Cisco names the cluster TLS verification setting as the condition. A standalone node is not in scope per the advisory.

  • The fix. X15.5.3 and earlier: first fixed release X15.5.20 (also shipped as Cisco's "Security Hardening Release: October 2026"). X14 and earlier: migrate. Cisco says "There are no workarounds that address this vulnerability." Cisco credits Stefan Aleksic of Jane Street with the report.

  • A public exploit. The repository github.com/dinosn/cve-2026-76466 was created Thursday, November 5, 2026 (GitHub API, 10:57 UTC). Its README says the attack reaches the Erlang distribution listener on TCP 4372 using a maintenance node name, wombat@127.0.0.1, and a cookie, both of which it says are baked in and identical on every affected install. The author says they validated it only on Expressway-C X15.3.2 in a two-node cluster in TLS Permissive mode, and did not test Expressway-E, X14 or the enforcing mode. So do not assume your cluster TLS setting saves you: upgrade.

  • Exploitation, per F6. F6's press release of Wednesday, November 18, says its incident responders investigated what it calls the first exploitation of this CVE. The victim was one company in Russia. Shortly after the public exploit appeared, attackers took root on two internet-facing Expressway X15.5.3 devices, then used one of them to reach two more cluster nodes inside the network. From there they staged homemade Python scripts to scan the network, find SMB shares, talk to SQL Server and WinRM, and go through GitLab repositories for credentials and other sensitive data. F6 says the attackers edited those scripts during the intrusion, and that comments in the code suggest an AI assistant wrote parts of them. F6 does not attribute the activity to a known group and does not give the date of the intrusion.


What is not confirmed


  • One source. Every exploitation report we found traces to F6. The Hacker News (November 20) cites F6. VulnCheck added the CVE to its KEV list on November 18 and cites F6's press release as the only exploitation reference. That is one incident response firm describing one victim, not several independent confirmations.

  • CISA has not listed it. CVE-2026-76466 is not in CISA's Known Exploited Vulnerabilities catalog as of catalog version 2026.11.18 (released Wednesday, November 18, 19:17 UTC; 1,786 entries), which we downloaded on November 20. No federal due date exists yet.

  • Cisco has not updated. The advisory we read is still version 1.0 of October 21, and it says Cisco PSIRT is "not aware of any public announcements or malicious use." That text predates F6's report.

  • No hashes, no domains. F6 published two IP addresses, one log line and one path pattern. No file hashes or domains.


What to do


  1. Upgrade clustered Expressway nodes on X15.5.3 or earlier to X15.5.20 or later. Plan a migration for anything on X14 or earlier.

  2. Fence the cluster ports until you do. F6 recommends allowing TCP 4371 and 4372 only from the IP addresses of trusted cluster peers. Cisco says no workaround fixes the bug; treat the firewall rule as exposure reduction, not a patch. On an Expressway-E in the DMZ, the internet should never reach these ports.

  3. Hunt on every node, including internal ones. F6's victim lost two internal nodes through an external one.

  4. If you find the log line, treat the cluster as compromised: isolate it, scope the network access it had, and rebuild on a fixed release rather than patching in place.


Am I affected?


Three questions, per node:


  • Which version? In the Expressway web interface, the software version is on the Status overview page. From an admin SSH session, the command xstatus SystemUnit Software Version prints it. X15.5.3 or earlier, or anything on X14, is vulnerable. X15.5.20 or later is fixed.

  • Is it clustered? Look under System, then Clustering. If the node has cluster peers configured, it is in scope. A standalone node is not, per Cisco.

  • Was it hit? Check erlang.log on each node for nodeup,'wombat@127.0.0.1', and check /mnt/harddisk/ for the i-plus-four-digits folders holding .py files. If you do not have shell access to the logs, a system snapshot from the Maintenance diagnostics pages or Cisco TAC can get them. We could not confirm the exact on-disk path of erlang.log from a public Cisco document; F6 names the file but not its folder.

There is no website check for this one. It is a flaw in a server's cluster service, not something a web page loads.



How we know, and what our edge saw


We read Cisco's advisory, F6's Russian-language press release (its English page returned a bot challenge to us; the Russian page loaded), the exploit's README and GitHub metadata, the CISA KEV JSON and VulnCheck's KEV entry.


The exploit rides Erlang distribution on TCP 4371-4372. Our edge sensors watch HTTP and HTTPS on our own sites, so they cannot see this protocol at all. That is a blind spot, not a clean result. We did look for F6's two IP addresses: across 636,223 edge block records, 156,326 edge canary records and 2,467 origin captures since September 1, 2026, neither address appears. Neither was in our feed before today. We make no claim to have seen this campaign first.



Indicators (from F6)


Block these: get the free feed (setup docs at docs.dugganusa.com). Both IPs are now in our feed at confidence 80 under source manual-batch-cisco-expressway-cve-2026-76466, credited to F6.


  • 66.179.31[.]32: hosting address, AbuseIPDB lists it in Singapore.

  • 18.130.47[.]116: an Amazon EC2 address in eu-west-2 (London). Cloud addresses get reassigned, so treat this one as time-bound.

  • Log line: nodeup,'wombat@127.0.0.1' in erlang.log on Expressway nodes.

  • Path: /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py


Timeline


  • Wednesday, October 21, 2026: Cisco publishes the advisory and X15.5.20.

  • Thursday, November 5: public exploit repository created on GitHub.

  • Wednesday, November 18: F6 publishes its incident report; VulnCheck adds the CVE to its KEV list.

  • Friday, November 20: not in CISA KEV as of catalog 2026.11.18; Cisco advisory still says no known malicious use.


Sources


  • Cisco, "Cisco Expressway Series Remote Code Execution Vulnerability," cisco-sa-vcs-static-cred-hr7EWZ8t: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t

  • F6 press release (Russian), November 18, 2026: https://www.f6.ru/media-center/press-releases/cisco-cve-2026-76466/

  • Public exploit README: https://github.com/dinosn/cve-2026-76466

  • The Hacker News, November 20, 2026: https://thehackernews.com/2026/11/hackers-exploit-critical-cisco.html

  • CISA KEV catalog JSON: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json





Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page