Cisco Expressway Bug Turned Into a Doorway Days After a PoC Dropped
F6 says attackers exploited critical Cisco Expressway flaw CVE-2026-76466 soon after a public PoC, took root on two internet-facing nodes, pivoted to two internal cluster peers and ran AI-assisted Python scripts hunting for credentials. X15.5.20 fixes it.
A month after Cisco patched it, the critical Cisco Expressway flaw CVE-2026-76466 is being used in real attacks. Russian security firm F6 says attackers took over two internet-facing Expressway devices at a Russian organization soon after a public proof-of-concept appeared, then used one of them to reach two more cluster nodes on the internal network, The Hacker News reports. With root on the boxes, they brought in Python scripts, which F6 believes were written with an AI assistant, to map the network and hunt for credentials. Cisco’s advisory still says it knows of no malicious use.
For defenders
The bug: CVE-2026-76466 (CVSS 9.8) is in the Expressway database service, used for clustering. Cisco says persistent cookies plus missing client-certificate validation when TLS Verify Mode is enabled let an unauthenticated attacker who has the cookies connect to the database service, call RPC commands and run anything as root. It affects Expressway-C and Expressway-E, virtual and appliance, but only clustered deployments, according to SecurityWeek. Fixed in X15.5.20 (October 21); X14 and earlier must move to a fixed release. Cisco lists no workarounds. A public exploit is reported on GitHub; not in CISA KEV.
Exploitation (KNOWN, per F6): the compromised devices ran X15.5.3, T1190 (Exploit Public-Facing Application). From root, the attackers staged Python scripts, T1059.006 (Command and Scripting Interpreter: Python), that scanned the network, T1046 (Network Service Discovery), found SMB shares, T1135 (Network Share Discovery), talked to SQL Server and WinRM, T1021.006 (Remote Services: Windows Remote Management), and searched GitLab, T1213.003 (Data from Information Repositories: Code Repositories), for credentials and other data. F6 says the scripts were edited during the attack. No actor is named.
Can’t patch today? F6 suggests blocking TCP 4371–4372 at the firewall for everything except the IP addresses of your own cluster peers.
66.179.31[.]32
18.130.47[.]116Python scripts under /mnt/harddisk/i{4 digits}{optional letter}/*.pyWhat it means for you
Expressway is the box that lets staff and partners join a company’s Cisco video calls and chat from outside the office. If your business doesn’t use Cisco’s calling and video systems, nothing to do here. If it does, the takeaway is simple: a device that sits on the internet’s edge was used as a doorway into the rest of the network, and the fix has been out for a month. Ask whoever manages it to confirm it’s on X15.5.20.
Do this now
- Update every Expressway node to X15.5.20; migrate anything on X14 or older.
- Until then, allow TCP 4371–4372 only between your own cluster nodes.
- Check
erlang.logforwombat@127.0.0.1and/mnt/harddiskfor unexpected Python scripts. - If you find either, assume the internal network was probed and rotate credentials kept in GitLab and on file shares.
Source article: Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network
Publisher: The Hacker News
Published: Nov. 20, 2026
URL: https://thehackernews.com/2026/11/hackers-exploit-critical-cisco.html
Executive Summary
An unattributed actor exploited CVE-2026-76466, a CVSS 9.8 flaw in the database service of clustered Cisco Expressway devices that lets an attacker holding the persistent cluster cookies invoke RPC commands and run operating system commands as root, against a Russian organization shortly after a public proof-of-concept appeared; Russian security firm F6 describes it as the first in-the-wild exploitation it has seen. The attackers first compromised two internet-facing Expressway X15.5.3 nodes, then pivoted through one of them into two more cluster nodes on the internal network. With root on the devices, they staged custom Python scripts that scanned the internal network, enumerated reachable SMB shares, interacted with SQL Server and WinRM, and searched GitLab repositories for credentials and other sensitive data; F6 says the scripts were modified during the attack and carried comments typical of an AI coding assistant. The objective appears to be credential and data theft from a foothold on a perimeter collaboration gateway, and the case shows clustering features turning one exposed node into a path to internal ones. Cisco fixed the flaw in X15.5.20 on October 21, 2026 and lists no workarounds; F6 advises restricting TCP 4371–4372 to trusted cluster peers. Hunt leads, false positive expectations and F6’s published indicators are detailed below; no detection rules or file hashes were published.
ATT&CK chain: Initial Access → Execution → Lateral Movement → Discovery → Collection → Credential Access
Hunt Lead Grid
| Hunt Lead Level | Hunt Lead Name | ATT&CK | Risk of False Positives |
|---|---|---|---|
| 1 (Junior) | F6 Expressway Compromise Artifacts | T1190 (Exploit Public-Facing Application), T1059.006 (Command and Scripting Interpreter: Python) | Low. The wombat@127.0.0.1 Erlang log entry and Python scripts in numbered folders under /mnt/harddisk are what F6 found on compromised nodes; the two IP addresses sit on hosting space that may be reassigned, so date any hit against November 2026. |
| 2 (Pro) | Database Service Ports Reached From Outside the Cluster | T1190 (Exploit Public-Facing Application) | Low. Only peer cluster nodes should ever connect to TCP 4371–4372; the rule anchors on a source that isn’t on the cluster peer list. |
| 3 (Elite) | Expressway Nodes Acting as Internal Scanners | T1046 (Network Service Discovery), T1135 (Network Share Discovery), T1021.006 (Remote Services: Windows Remote Management), T1213.003 (Data from Information Repositories: Code Repositories) | Medium. Expressway legitimately talks to CUCM, IM and Presence, DNS, NTP and LDAP; the correlation anchors on it reaching ports and hosts outside that set (SMB, MSSQL, WinRM, GitLab) or many hosts in a short window, compared against its own baseline. |
F6 Expressway Compromise Artifacts
F6 found that the attackers, once they had root through CVE-2026-76466, left a trace in the Erlang system log of the affected devices: an entry containing wombat@127.0.0.1 in erlang.log. They staged their Python tooling in folders whose names follow the pattern /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/ (the letter i, four digits and an optional letter) containing *.py files, and connections tied to the activity came from 66.179.31[.]32 and 18.130.47[.]116. The detection is a direct check of every Expressway node’s erlang.log for the wombat@127.0.0.1 string, a file listing of /mnt/harddisk for folders matching that pattern or any .py file that isn’t part of the Cisco software, and a search of firewall, NetFlow and Expressway logs for the two addresses.
Collect the logs through the Expressway web interface or a support bundle (diagnostic logging) if you don’t have shell access, and pull firewall and NetFlow history for the edge interfaces. Check every node in a cluster, internal ones included, because the attackers pivoted from an edge node to internal peers. Sweep back to the PoC’s release and ideally to October 21, 2026, when the advisory came out. Blocking the two IP addresses is fine but weak, since exploitation needs nothing more than network access and the addresses will change. Any hit should be escalated: the node should be rebuilt from a fixed image rather than cleaned, and anything it could reach should be treated as exposed.
Hunt Lead Level: 1 (Junior Analyst)
ATT&CK: Initial Access → T1190 (Exploit Public-Facing Application); Execution → T1059.006 (Command and Scripting Interpreter: Python)
Sources: “Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network”, The Hacker News, Nov. 20, 2026, https://thehackernews.com/2026/11/hackers-exploit-critical-cisco.html (source article)
Database Service Ports Reached From Outside the Cluster
Cisco’s advisory says the flaw is reached by connecting to the Expressway database service with the persistent cookies and invoking RPC commands, and that client certificates aren’t validated when TLS Verify Mode is enabled for clustering. F6’s workaround of blocking TCP 4371–4372 except from trusted cluster nodes, reported by SecurityWeek, identifies those ports as the clustering path. In the F6 case, the attackers came in on two internet-facing nodes and then reached two internal cluster nodes through one of them. The detection logic is any inbound connection to TCP 4371 or 4372 on an Expressway node from an address that isn’t one of that node’s configured cluster peers, and, separately, any connection on those ports from an edge node to an internal node outside the normal replication pattern (for example a new session after a long quiet period, or traffic volumes far above baseline).
Use perimeter and internal firewall logs or NetFlow, and take the peer list from each cluster’s configuration. Internet-sourced traffic to these ports should be zero, so any accepted connection from the internet is an incident rather than something to tune. Keep it scoped to Expressway addresses; the ports aren’t unique to Cisco, so a network-wide rule would be noisy. Blocking the ports is the right short-term control, but don’t block peer-to-peer traffic between legitimate cluster members, since that breaks replication. Escalate any hit, collect the node’s logs for the Junior lead above and check whether the source address also scanned other edge services. The lead applies to any clustered appliance whose replication channel is exposed beyond its peers.
Hunt Lead Level: 2 (Pro)
ATT&CK: Initial Access → T1190 (Exploit Public-Facing Application); Lateral Movement → T1210 (Exploitation of Remote Services) for the edge-to-internal pivot
Sources: “Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network”, The Hacker News, Nov. 20, 2026 (source article); “Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release”, SecurityWeek, Nov. 19, 2026, https://www.securityweek.com/hackers-exploit-cisco-expressway-vulnerability-soon-after-poc-release/ (additional source, same incident)
Expressway Nodes Acting as Internal Scanners
After gaining root on the internal cluster nodes, the attackers ran custom Python scripts that scanned the network, discovered reachable SMB resources, interacted with SQL Server and WinRM, and accessed GitLab repositories to collect credentials and other sensitive data. F6 says the scripts were changed on the fly during the intrusion. An Expressway node’s normal conversation partners are narrow: Unified CM, IM and Presence, its cluster peers, DNS, NTP, syslog, LDAP for authentication and the edge or core counterpart. The correlation to build is an Expressway address as the source of connections to TCP 445, 1433, 5985 or 5986, or to a GitLab server’s HTTP(S) or SSH ports, or of connection attempts to more than a handful of distinct internal hosts within a short window, joined with authentication events on the targets that show logons or API access coming from the Expressway address.
Join internal NetFlow or firewall logs with Windows Security logs (4624 and 4625 network logons, WinRM operational logs), SQL Server login auditing and GitLab audit and access logs, filtering on the Expressway IP addresses as the client. Baseline each node’s destinations over 30 days and alert on any new destination port class; most environments will find the baseline is very small. Sweep back to October 21, 2026. Don’t rely on host-based detection, since Expressway runs no EDR; the network and target-side logs are the only practical view. A hit means the node is an active pivot: isolate it, then rotate credentials stored in reachable GitLab projects, shares and SQL logins, because those were the stated targets. The lead generalises to any compromised network appliance used as a launch point for internal discovery.
Hunt Lead Level: 3 (Elite)
ATT&CK: Discovery → T1046 (Network Service Discovery), T1135 (Network Share Discovery); Lateral Movement → T1021.006 (Remote Services: Windows Remote Management); Collection → T1213.003 (Data from Information Repositories: Code Repositories)
Sources: “Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network”, The Hacker News, Nov. 20, 2026 (source article); “Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release”, SecurityWeek, Nov. 19, 2026 (additional source)
Hash Appendix
Attacker Python scripts
No file hashes were published in the source article or the additional source, and F6’s own report could not be retrieved (bot protection). No hashes were looked up in OTX AlienVault or VirusTotal for this report.
MD5s
(not available) # *.py -> attacker scanning and collection scripts in /mnt/harddisk/i####x/
SHA1s
(not available) # *.py -> attacker scanning and collection scripts in /mnt/harddisk/i####x/
SHA256s
(not available) # *.py -> attacker scanning and collection scripts in /mnt/harddisk/i####x/
References Appendix
- “Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network”, The Hacker News, Nov. 20, 2026, https://thehackernews.com/2026/11/hackers-exploit-critical-cisco.html
- “Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release”, SecurityWeek (Eduard Kovacs), Nov. 19, 2026, https://www.securityweek.com/hackers-exploit-cisco-expressway-vulnerability-soon-after-poc-release/
- Cisco Security Advisory cisco-sa-vcs-static-cred-hr7EWZ8t, Cisco, Oct. 21, 2026, https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t
CVE at a glance
- CVSS
- 9.8 Critical (v3.1)
- EPSS
- 0.4% chance of exploitation in the next 30 days (higher than 36.8% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 20, 2026
- Public exploit
- Yes, reported in 1 GitHub repository
Data from NVD, FIRST EPSS and CISA KEV, refreshed automatically. We report whether public exploit code exists but never link to it: fake proof-of-concepts that infect researchers are common.