Attackers rooted Cisco Expressway clusters after exploit code for a fixed flaw went public
Security firm F6 says attackers used Cisco Expressway flaw CVE-2026-76466 to take root on four devices at a Russian organization after a public exploit appeared. Cisco's fix, X15.5.20, has been out since October 21.
Warden, covering security, outages and the rules for tech
, 2 min read
X15.5.20Fixed Expressway release; no workaround exists
What to know
- CVE-2026-76466 (CVSS 9.8) lets an unauthenticated attacker run commands as root on clustered Cisco Expressway devices.
- F6 says attackers breached two internet-facing Expressway devices at a Russian organization, then two more cluster nodes, after exploit code was posted on GitHub.
- Cisco fixed the flaw on October 21 in Expressway X15.5.20; X14 and earlier must migrate to a fixed release.
This one was never a zero-day. Cisco shipped the fix on October 21, exploit code was on GitHub by November 12, and on Thursday, November 19, security firm F6 reported what it called the first case of attackers using it. That is 29 days from patch to published attack, and any cluster left on X15.5.3 or older spent them exposed.
The flaw, CVE-2026-76466, is rated 9.8 out of 10. It lets an attacker with no credentials run commands as root on Cisco Expressway, the gateway many companies use to connect video calls and phones to the outside world. Only clustered devices are affected, both the Core (Expressway-C) and Edge (Expressway-E) roles, virtual or physical. Cisco's advisory, as quoted by The Hacker News, blames persistent cookies in the database service and weak checks of client certificates when TLS Verify Mode is on for clustering. Cyber Press, which covered the public exploit, describes it as a hard-coded credential in the cluster manager.
Who needs to do what
The fix is Expressway X15.5.20. Anyone on X15.5.3 or earlier upgrades to it; X14 and earlier must migrate to a fixed release. Cisco offers no workaround, according to Daily Security Review and Cyber Press. Cyber Press suggests limiting the cluster ports, TCP 4371 and 4372, to cluster peers, but that's its own advice, not Cisco's. Daily Security Review says the advisory still states Cisco is not aware of malicious use; we could not load Cisco's page to confirm.
What F6 found
We could not load F6's report either; this comes from The Hacker News and Security Affairs, which agree. The attackers broke into two internet-facing Expressway devices running X15.5.3, used one of them to reach two more cluster nodes, and took root on all of them. They then readied custom Python scripts to scan the internal network, find file shares, connect to SQL Server and Windows Remote Management, and dig through GitLab repositories for credentials and data. The Hacker News says the scripts may have been written with help from AI tools. F6 named no group and gave no attack dates.
Signs to check, per The Hacker News: a "nodeup" entry for a node called "wombat" in the Erlang log, unexpected Python scripts on the device's hard disk, and the two IP addresses F6 published.
The flaw is not in CISA's Known Exploited Vulnerabilities catalog, and no source says it is. The contrast with this week's vCenter zero-day is the useful part: there, defenders had no patch for months. Here they had one for a month, and the clock that mattered started when the exploit went public. Earlier this week attackers also hit Apache Roller with a flaw that had a fix. Our guide to reading a security advisory explains why "not aware of malicious use" is a statement about the day it was written.
Sources
- Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network, The Hacker News, November 20, 2026
- Hackers Exploit Cisco Expressway Flaw CVE-2026-76466 After PoC Leak, Daily Security Review, November 20, 2026
- Hackers Exploit Cisco Expressway Flaw CVE-2026-76466 to Breach Russian Organization, InfoSec Today (Security Affairs), November 20, 2026
- Critical Cisco Expressway Flaw Allows Hackers to Execute Root Commands, Public PoC Released, Cyber Press, November 12, 2026
Internet, outages and security
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.