
November 20, 2026
Attackers have exploited a critical remote code execution flaw in clustered Cisco Expressway devices, tracked as CVE-2026-76466 (CVSS 9.8), shortly after proof-of-concept exploit code was posted on GitHub. Russian security firm F6 says it investigated one intrusion at an organization in Russia, where attackers compromised two internet-facing Expressway devices and used one of them to reach two additional cluster nodes on the internal network.
What’s known about the flaw
Cisco disclosed CVE-2026-76466 on October 21, 2026, in advisory cisco-sa-vcs-static-cred-hr7EWZ8t, and released fixes the same day. The flaw lets an unauthenticated remote attacker with network access run operating system commands as root on Expressway-C and Expressway-E devices.
It sits in the Expressway database service and only affects virtual and appliance deployments configured as a cluster. Cisco attributes it to the use of persistent cookies, combined with insufficient client certificate validation when TLS Verify Mode is enabled for clustering. An attacker who has the cookies can connect to the database service and invoke specific remote procedure call (RPC) commands.
At disclosure, Cisco said it was not aware of public exploits or malicious use. A proof-of-concept exploit has since been published on GitHub [date PoC appeared: not confirmed].
How the attack unfolded
F6 says the attackers first breached two internet-facing Expressway X15.5.3 devices. Through one of them, they gained access to two additional cluster nodes on the organization’s internal network.
With root access, the attackers used custom Python scripts for lateral movement. According to F6, the scripts scanned the network, discovered accessible SMB resources, interacted with SQL Server and WinRM, and accessed GitLab repositories to collect credentials and other sensitive data.
F6 says the scripts appear to have been developed with help from AI tools, based on comments and descriptions of fixes left in the code. F6 did not name the targeted organization, and the attack has not been attributed to any known threat actor.
Indicators of compromise
F6 published these indicators:
- IP addresses: 66.179.31[.]32 and 18.130.47[.]116
- Log entry: “wombat@127.0.0.1” in the Erlang system log (erlang.log) on affected Expressway devices
- File path pattern: Python scripts staged under /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py
What defenders should do
Standalone Expressway nodes are not affected by this flaw, but clustered Expressway-C and Expressway-E deployments are. Cisco lists no workarounds.
For Expressway Release X15.5.3 and earlier, the fix is Release X15.5.20. Organizations on Release X14 or earlier have no fix in their branch and must migrate to a fixed release.
If you can’t upgrade right away, F6 advises limiting firewall access to TCP ports 4371 and 4372 so only trusted cluster node IP addresses can connect. F6 also recommends auditing environments for signs of compromise, isolating affected systems, determining the scope of the attack, and blocking potential lateral movement paths.
F6 notes that compromise of a perimeter device can open a path to an organization’s critical systems, so defenses should include segmentation and infrastructure monitoring as well as timely patching.
Sources: Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t) · F6 press release (https://f6.security/media-center/press-releases/cisco-vulnerability-exploitation/)

Leave a Reply