November 20, 2026
← All advisories

Cisco Expressway Root Flaw Now Exploited and on CISA KEV List

Red Tiger Security infographic: Cisco Expressway flaw CVE-2026-76466, rated critical at 9.8, is now exploited and on the CISA Known Exploited Vulnerabilities catalog. Hard-coded cluster credentials give root on clustered Expressway-C and Expressway-E, fixed in X15.5.20 with no workarounds. A left-to-right timeline: 21 October 2026, Cisco advisory and fix; then public proof-of-concept exploit code; 18 November, security firm F6 reports an attack on a company in Russia; 20 November, CISA adds it to the catalog; 23 November, federal due date. How the attack moved per F6: from the internet with no login, to root on two edge devices, to two internal cluster nodes, to scripts hunting for credentials. Four steps: upgrade to X15.5.20, allow TCP ports 4371 and 4372 only from cluster peers, check erlang.log for a wombat@127.0.0.1 entry and stray Python scripts, and keep these servers away from the control system.

The Cybersecurity and Infrastructure Security Agency (CISA) added a critical Cisco Expressway flaw, CVE-2026-76466, to its Known Exploited Vulnerabilities (KEV) catalog on Friday, 20 November 2026. CISA gave United States federal civilian agencies until Monday, 23 November 2026 to act, a three-day window, and its catalog entry also points agencies to its forensic triage requirements, so they are expected to look for signs of compromise and not only patch.

Cisco Expressway is a gateway that lets remote staff, partners and outside users reach an organization's voice, video and messaging services. The series includes Expressway Core (Expressway-C), which sits inside the network, and Expressway Edge (Expressway-E), which usually faces the internet. Cisco published advisory cisco-sa-vcs-static-cred-hr7EWZ8t on 21 October 2026 and rates the flaw 9.8 out of 10 on the Common Vulnerability Scoring System (CVSS). It falls under Use of Hard-coded Credentials (CWE-798).

Cisco says the problem sits in the database service that clustered Expressway devices use to talk to each other. The devices use persistent cookies, and when the cluster's Transport Layer Security (TLS) verify mode is enabled, client certificates are not actually checked. An attacker who has those cookies and can reach the database service, with no login at all, can send specific remote procedure call (RPC) commands and run any operating system command as root, the highest level of control on the device.

Affected: Expressway-C and Expressway-E, both virtual and appliance versions, only when they are configured in a cluster and running a vulnerable release. Release X15.5.3 and earlier should move to X15.5.20, the first fixed release. Release X14 and earlier must migrate to a fixed release. Cisco says there are no workarounds. The fix is also part of Cisco's Expressway Series Security Hardening Release of October 2026.

What changed: on 18 November 2026, the Russian security firm F6 reported what it calls the first known exploitation, against one company in Russia, shortly after a public proof-of-concept exploit appeared. According to F6, the attackers took root control of two internet-facing Expressway X15.5.3 devices, used one of them to reach two more cluster nodes on the internal network, and then staged Python scripts to scan the network, look for file shares, SQL Server and Windows Remote Management (WinRM) access, and search code repositories for credentials. F6 did not name the attacker. Cisco's advisory, still at version 1.0, says Cisco is not aware of malicious use, but CISA's KEV listing means CISA now has evidence of exploitation.

Why this matters for plant owners: Expressway is not an industrial control product, but it often sits at the edge of the business network or in the demilitarized zone (DMZ) of utilities, plants and pipeline companies, carrying video calls for control rooms, remote sites and vendors. The F6 case shows the pattern we worry about most. Attackers start on an internet-facing gateway, move through the cluster to systems inside the network, and go looking for credentials. If the business network can reach the control system, a foothold on an edge gateway becomes a path toward operations.

What to do now

  1. Find every Expressway-C and Expressway-E you own, check the release and whether the devices are clustered, and upgrade to X15.5.20 through your normal change control. Devices on X14 or earlier need a migration plan now.
  2. Until the upgrade is done, limit who can reach the cluster database service. F6 recommends allowing Transmission Control Protocol (TCP) ports 4371 and 4372 only from the addresses of trusted cluster peers. Keep management interfaces off the internet.
  3. Review each device for signs of compromise. F6 lists a nodeup entry for wombat@127.0.0.1 in the Erlang system log (erlang.log) as a key sign of exploitation, along with unexpected Python scripts on the device. If you find anything, treat the cluster and any accounts it touched as compromised, and work with Cisco's Technical Assistance Center (TAC).
  4. Confirm that the Expressway servers and the rest of the business network cannot reach the control system directly. Traffic into operations should pass through a firewall and the DMZ with only the connections you need, and new connections from collaboration servers should raise an alert in your security operations center (SOC).

Red Tiger can help you see what your edge devices can reach. During our onsite facility assessments, our team walks the system from the perimeter through the DMZ and control room down to the field devices, and we often find business systems such as video and voice gateways with more reach into operations than anyone intended. We can then help remediate and harden what we find, and we can install a firewall and sensor at the site, connect them to the Red Tiger 24x7 SOC, and monitor the site for ongoing detection and response, with regular metrics and reports. Our team has completed more than 500 assessments and trained more than 4,500 people.

We are here to help, so check out our resources online at www.redtigersecurity.com and book a follow-up call with our team if you have any questions: https://calendly.com/jonathanpollet/30min

Source: Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t, 21 October 2026, and the CISA Known Exploited Vulnerabilities catalog entry, 20 November 2026: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t

← All advisories

Cite this advisory: Red Tiger Security, "Cisco Expressway Root Flaw Now Exploited and on CISA KEV List", November 20, 2026, https://www.redtigersecurity.com/advisory/cisco-expressway-cve-2026-76466-kev

Read the original source →

We are here to help.

Check out our resources and book a follow-up call with our team.

+1.877.387.7733