A critical flaw in Cisco Expressway has moved from "patch soon" to "patch now." Attackers have already used it to break into a company's devices and reach its internal network, and on 20 November CISA added the flaw to its Known Exploited Vulnerabilities catalogue, giving US federal agencies until Monday, 23 November to fix it. The patch has actually existed for a month — Cisco released it on 21 October — which is exactly the problem: the attackers are finding the systems nobody updated.
If your organisation runs Cisco Expressway in a cluster, this one needs your weekend, not your next patch cycle.
What Cisco Expressway does
Expressway is Cisco's gateway for collaboration traffic. It lets remote employees, partners and outside callers securely reach an organisation's video meetings, voice calls and messaging without a VPN. Expressway-C sits on the inside as the core, Expressway-E sits at the edge facing the internet, and the two are often run as a cluster so several nodes share the load and back each other up.
That position — internet-facing, trusted by the inside network, and carrying the company's calls — is what makes a flaw in it so valuable to attackers.
The flaw: CVE-2026-76466
The vulnerability, tracked as CVE-2026-76466, scores 9.8 out of 10 and sits in the database service that Expressway nodes use when they run as a cluster. Cisco classifies it as a hard-coded credentials problem. In plain terms: the cluster service relies on persistent cookies, and when clustering is set up with TLS Verify Mode enabled, the devices do not check client certificates strictly enough. An attacker who holds the right cookies can connect to the database service and issue commands that run as root — the highest level of control on the device. No username and password are needed.
The important limits:
Only clustered deployments are affected — both Expressway-C and Expressway-E, virtual and appliance versions.
Releases X15.5.3 and earlier are vulnerable.
The fix is release X15.5.20. Systems on X14 or earlier get no patch on their own branch and must migrate to a fixed release.
Cisco lists no workaround. Patching or migrating is the only fix.

How the attack worked
A public proof-of-concept exploit appeared on GitHub on 5 November. Two weeks later, on 19 November, Russian security firm F6 reported what looks like the first real-world attack.
According to F6, the attackers hit a Russian organisation running Expressway X15.5.3. They first broke into two internet-facing Expressway devices, then used the trust between cluster nodes to pivot sideways into two more nodes sitting on the internal network — the edge boxes were the door, not the target. With root access, they dropped custom Python scripts built to move through the network: scanning file shares, probing SQL Server and Windows remote management, and searching the company's GitLab repositories for credentials and other sensitive data. F6 noted the scripts carried comments suggesting they were written or adjusted with help from an AI assistant, and modified while the attack was running.
F6 did not name the victim, and no group has been blamed. But the pattern — public exploit code, then a real intrusion within days — is one defenders have seen again and again this year.
Why CISA set a Monday deadline
CISA does not add flaws to its Known Exploited Vulnerabilities list on suspicion; a flaw gets in when there is evidence attackers are using it. CVE-2026-76466 was added on 20 November, one of four flaws added the same day — the list also gained the VMware vCenter zero-day, an Apache Roller flaw and a SAP NetWeaver flaw, all with the same 23 November deadline for federal agencies.
Private companies are not legally bound by that deadline, but they should treat it as a signal: this is being exploited now, the exploit code is public, and every unpatched cluster is a standing invitation.

What to do now
Patch every node in the cluster to X15.5.20. Do not leave one old node behind — the attackers in the F6 case used the cluster link itself to move from the edge to the inside. If you run X14 or earlier, migrate to a fixed release instead.
If you cannot patch today, limit the blast radius. Cisco offers no workaround, but F6 recommends blocking the cluster database ports (TCP 4371–4372) at the firewall so only trusted cluster nodes can reach them. This reduces exposure; it is not a fix.
Hunt for signs you were already hit. F6 shared indicators from the attack: check the Erlang system log (erlang.log) on each Expressway device for a nodeup event from the node name "wombat@127.0.0.1"; look for Python scripts stored under /mnt/harddisk/ in folders with names like i1234; and check for connections from the IP addresses 66.179.31.32 and 18.130.47.116.
If you find anything, treat it as a breach, not a near miss. The attackers went looking for credentials — rotate service-account passwords and any tokens stored in systems they could have reached, such as GitLab, and check the internal systems their scripts probed.
Put edge appliances into your normal patch cycle. Expressway, VPN gateways and similar edge devices are exactly where attackers look first, because they are internet-facing and trusted. A collaboration gateway should never sit a month behind on a critical fix.
The real lesson
Nothing about this story required a new discovery. Cisco shipped the fix on 21 October. The exploit code arrived on 5 November. The first known victim was breached running the old version anyway. The gap between "patch available" and "patch applied" is where most intrusions now live — and clustered edge devices, which nobody wants to take offline because the phones and meeting rooms depend on them, are where that gap gets widest.
If you run Cisco Expressway, close the gap this weekend: X15.5.20 on every node, then check the logs. Monday's deadline is CISA's. The attackers are not waiting for it.
Sources: The Hacker News and SecurityWeek reported the exploitation on 20 November 2026, based on research by security firm F6; CISA added CVE-2026-76466 to its Known Exploited Vulnerabilities catalogue on 20 November 2026 with a 23 November remediation deadline; Cisco's advisory was first published on 21 October 2026.




