November 20, 2026

From Advisory to Breach: A Timeline of How Attackers Turned a Cisco Expressway Bug Into a Path Inside the Network

A month after Cisco patched a critical root-level flaw in its Expressway video collaboration gateways, researchers have documented the first known break-in using it: two internet-facing devices, two internal cluster nodes and a push toward databases and code repositories. Here is how it unfolded.

An empty corporate video conference room with a wall display, a small camera and a long table

Cisco Expressway devices sit at the network edge, where some of them face the internet, and that position makes them attractive to attackers. A newly published investigation shows what happened at one organization that was still running a vulnerable version. The sequence below is based on The Hacker News’ report on findings from the Russian security firm F6, whose investigation involved a Russian organization.

The timeline

October 21: Cisco ships the fix

Cisco released patches for CVE-2026-76466, rated 9.8 out of 10. Its advisory said the bug stems from the use of persistent cookies, combined with client certificates not being validated when TLS Verify Mode is enabled for clustering. An attacker who holds those cookies can connect to the device’s database service, call certain remote procedure commands and run operating system commands as root, without logging in. Version X15.5.20 contains the fix; customers on X14 or earlier must migrate to a fixed release.

After that: exploit code goes public

A proof-of-concept exploit was published. The report does not give an exact date, but F6 says the attack it investigated followed that release.

Step one of the intrusion: two devices at the edge

The attackers compromised two internet-facing Expressway devices running X15.5.3 and gained root on them.

Step two: into the internal cluster

Through one of those devices, they reached two more Expressway cluster nodes sitting on the organization’s internal network, bringing the total to four compromised devices.

Step three: looking for what matters

Using custom Python scripts, the intruders scanned the network, hunted for reachable SMB file shares, interacted with SQL Server and Windows Remote Management, and accessed GitLab repositories in an effort to collect credentials and other sensitive data. F6 noted that comments and fix descriptions in the scripts suggest they may have been written with help from AI tools.

November 19: the report

F6 published its findings on Thursday, describing it as what appears to be the first in-the-wild exploitation of the flaw. The activity has not been tied to any known group. F6 shared indicators, including two IP addresses, the string “wombat@127.0.0.1” appearing in the Erlang system log (erlang.log) on affected devices, and Python scripts staged under the /mnt/harddisk directory.

What F6 says the lesson is

The firm’s conclusion is that a compromised perimeter device can open a path to an organization’s critical systems, so protection has to include not just fast patching but properly configured segmentation and infrastructure monitoring. Its advice to Expressway customers is to update to a supported fixed version, audit for signs of compromise, isolate affected systems, work out how far the attack reached and block routes for lateral movement.

What this means for your company

Most small and midsize businesses do not run Expressway, but almost all of them run something like it: a firewall, VPN, remote access box, phone system or video gateway that faces the internet and quietly trusts the network behind it. Keep a list of every such device and who is responsible for patching it, and treat critical fixes for them as same-week work, because a month was enough time for exploit code to appear here. Make sure edge devices cannot freely reach file shares, databases, management interfaces and code repositories on the inside. Watch for those devices behaving like workstations, such as scanning the network or logging in to servers. And if a critical edge patch sat unapplied for weeks, check for compromise after you install it.

If you want a second set of eyes on what sits at the edge of your network and what it can reach inside, we can help you map it and tighten it. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author