Cisco Expressway CVE-2026-76466 exploited in the wild: root, hours after the PoC

by | Nov 20, 2026 | Tutorials | 0 comments

Attackers have been exploiting a critical flaw in Cisco Expressway within days of a working proof-of-concept exploit appearing publicly, according to a report published Thursday by the Russian security firm F6. The company says it observed what appears to be the first in-the-wild use of the vulnerability to gain remote code execution with root privileges on an internet-facing Cisco Expressway X15.5.3 device.

What the flaw actually is

The bug is tracked as CVE-2026-76466 and carries a CVSS score of 9.8. Cisco’s advisory, released in late October, describes an unauthenticated remote attacker with network access to an affected device being able to run arbitrary operating system commands as root.

The mechanism matters more than the score. Cisco attributes the flaw to two things stacking: the use of persistent cookies, and insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering. An attacker holding valid cookies can connect to the database service and invoke specific remote procedure calls. Those calls run with root privileges on the underlying operating system.

That combination is why this is not just another patch-Tuesday item. The trust relationship built for clustering becomes the entry point, and the payoff is root, not a foothold.

How far the attackers got

F6’s account describes a short path from the edge to the interior. The attackers first compromised two internet-facing Cisco Expressway devices. Through one of them they reached two additional cluster nodes sitting on the organization’s internal network, meaning a single exposed appliance handed over the cluster.

With root, they moved laterally. F6 reports custom Python scripts used to scan the network, discover accessible SMB resources, interact with SQL Server and WinRM, and reach GitLab repositories. The stated goal was credential and data theft rather than disruption.

One detail worth pausing on: analysis of the scripts found comments and descriptions of fixes, which F6 says suggests they may have been developed with the help of AI tooling. That is an observation about the tooling, not attribution. The activity has not been tied to any known threat group.

What to do

  • Patch, and patch the cluster. Cisco released fixes on 21 October 2026. X15.5.3 and earlier move to X15.5.20. Release X14 and earlier must migrate to a fixed release, because there is no in-place patch for those trains. Fixing one node leaves the trust relationship between nodes intact, so treat the whole cluster as the unit of work.
  • Check the Erlang log. The published indicator is the string [email protected] appearing in erlang.log on affected devices.
  • Look for staged scripts. The second indicator is Python files dropped in paths matching /mnt/harddisk/i[0-9]{4}[a-zA-Z]?/*.py. Anything there that you did not put there is worth reading before you delete it.
  • Hunt the two IPs. The reported command-and-control addresses are 66.179.31[.]32 and 18.130.47[.]116. Check egress logs and any firewall or proxy records that survive.
  • Rotate what the appliance could reach. If a box had root and network access, treat every credential it could touch as exposed: directory and SMB accounts, SQL Server logins, WinRM credentials, GitLab tokens, API keys in config files.
  • Take the management plane off the internet. The exploit needs network access to the device. Where Expressway does not have to answer on a public address, it should not.

The part that generalises

The uncomfortable lesson is the timeline. A proof-of-concept went public and exploitation followed almost immediately, against an appliance many organizations treat as infrastructure and patch on a quarterly rhythm. Edge devices are now the shortest path into a network, and the gap between disclosure and weaponisation is measured in hours, not weeks.

If you run Expressway, the practical order is: confirm the version, patch every node, then go looking in the logs for what happened before you did.

Sources: The Hacker News, Security Affairs and SecurityWeek coverage of the F6 report, and Cisco’s security advisory for CVE-2026-76466.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

avatart

About

I’m a System Administrator and a developer with 10+ years of experience.