On this page
Attackers are using a bug in Cisco Expressway, the gateway many companies put in front of their Cisco calling and video systems so staff can call and meet from outside the office, to run their own commands with full control of the box. On November 20, 2026 CISA added CVE-2026-76466 to its Known Exploited Vulnerabilities (KEV) catalog with a deadline of Monday, November 23. Cisco fixed it a month ago, on October 21, in Expressway X15.5.20. Only Expressways that run as a cluster are affected.
One detail worth knowing before you read Cisco's page: as of November 20 the advisory is still version 1.0 from October 21, and it still says Cisco PSIRT "is not aware of any public announcements or malicious use". CISA's listing is the newer fact. Don't let the vendor page talk you into waiting for the next maintenance window.
How to fix
Upgrade to the fixed release. From Cisco's fixed-software table:
- Expressway X15.5.3 and earlier X15 releases: upgrade to X15.5.20.
- Expressway X14 and earlier: Cisco has no fix on that train. Its table says "Migrate to a fixed release", which means moving to X15.5.20.
Cisco lists no workarounds. To see what you run, sign in to the Expressway web interface and read Software version on Status > Overview, or over SSH as admin run:
xstatus SystemUnit
and read the Software Version line. Do this on every peer, Expressway-C and Expressway-E.
Clusters need the upgrade done in order. Cisco's administrator guide says to back up first (Maintenance > Backup and restore), upgrade the primary peer first and then the other peers one at a time, and do the Expressway-E cluster before the Expressway-C cluster. Afterward, System > Clustering should show the cluster database as Active on every peer. The same X15.5.20 release also carries Cisco's October hardening fixes for eight other Expressway CVEs, which Cisco says were found internally and are not known to be exploited.
Are you in scope? Check one page
Open System > Clustering on the Expressway. If the peer address fields list other peers, the box is clustered and this bug applies until you are on X15.5.20. If the peer fields are empty, the box is standalone and Cisco's advisory does not cover it.
While the upgrade is scheduled, check who can reach the cluster ports. Cisco's clustering guide lists TCP 4371 and 4372 as the ports peers use for cluster database sync and communication, and recommends firewall rules that drop TCP to both ports from everything except the other peers (System > Protection > Firewall rules > Configuration). From a machine that is not a peer:
nc -vz -w 5 expressway-e.example.com 4372
A refused or timed-out connection is what you want. If it connects, anyone on that network path can talk to the service this bug lives in. Cisco's advisory does not name the port, so treat this as a way to shrink who can try, not as a fix.
What the bug is
Cisco describes it as a flaw in the database service that Expressway peers use to stay in sync. Two things go wrong together. The service uses persistent cookies, and Cisco files the bug as hard-coded credentials (CWE-798). And when cluster TLS verification is turned on, the service still does not validate client certificates. Someone who holds the cookies and can reach the service can call specific remote procedure commands and run anything they want as root on the underlying operating system.
Cisco has not said how an attacker gets the cookies or whether they are the same on every device. Until it does, assume a stranger who can reach the service may already have what they need.
Cisco rates it Critical, CVSS 9.8, and both Cisco and CISA describe the attacker as unauthenticated and remote.
After you patch: look for a break-in
CISA marked this entry "Forensic Triage: Yes". Under BOD 26-04 that means federal agencies must patch within three days and also check whether the device was compromised. CISA's triage guidance puts evidence collection before patching when possible, because an upgrade reboots the appliance and wipes what was in memory. A practical order for an Expressway peer:
- Take a full backup and download the logs from the web interface before you touch the software. A system snapshot from Maintenance > Diagnostics captures logs and configuration in one file.
- If the Expressway is a virtual machine, snapshot it with memory first.
- Upgrade in cluster order as above.
- Review admin accounts and recent configuration changes on the primary peer. Cluster configuration replicates from the primary, so a change an attacker made there spreads to every peer.
Cisco has not published indicators of compromise for this bug. If something looks wrong, open a case with Cisco TAC before you rebuild.
Who is not in scope
- Standalone Expressways that are not in a cluster. Cisco limits this advisory to devices "configured in a cluster". They still get the October hardening fixes in X15.5.20.
- Other Cisco calling products such as Unified Communications Manager. Cisco says only the products in the advisory's vulnerable list are known to be affected.
- Webex cloud meetings themselves. This is a bug in the gateway appliance or VM you run.
What this is not
This is not something a caller can trigger by dialing in or joining a meeting. It needs network access to the cluster database service plus the cookies. It is also not fixed by a setting: Cisco lists no workaround, and turning on cluster TLS verification does not help, because the advisory says client certificates go unchecked in that mode.
HOL Guard keeps the source record for this issue in the CVE-2026-76466 evidence pack. This post is the operator write-up.
What do people ask about the Cisco Expressway KEV bug?
Is CVE-2026-76466 being exploited?
Yes, according to CISA, which added it to the Known Exploited Vulnerabilities catalog on November 20, 2026. Cisco's advisory, last revised October 21, still says Cisco is not aware of malicious use.
Which Expressway version fixes CVE-2026-76466?
X15.5.20. Expressway X14 and earlier must migrate to a fixed release; Cisco has no fix on those trains.
Is a standalone Expressway affected?
Not by this CVE. Cisco says the bug affects Expressway-C and Expressway-E, virtual and appliance, only when configured in a cluster.
Is there a workaround?
No. Limiting TCP 4371 and 4372 to the other cluster peers cuts down who can reach the service, but Cisco's only fix is the upgrade.
What is the CISA deadline?
November 23, 2026, with forensic triage required. It binds US federal civilian agencies; everyone else should read it as a signal of urgency.
Related
- VMware vCenter CVE-2026-123890, added to KEV the same day
- Cisco ASA and FTD SSL VPN CVE-2026-76418 on CISA KEV
- Cisco Secure Email Gateway CVE-2026-76519 on CISA KEV
- Cisco SD-WAN Manager CVE-2026-76504 on CISA KEV
- HOL Guard CVE index
References
- Cisco: cisco-sa-vcs-static-cred-hr7EWZ8t, Cisco Expressway Series Remote Code Execution Vulnerability
- Cisco: Cisco Expressway Series Security Hardening Release: October 2026
- Cisco: Expressway Cluster Creation and Maintenance Deployment Guide (X15.4)
- Cisco: Expressway Administrator Guide (X15.5), Maintenance and cluster upgrade order
- CISA: Known Exploited Vulnerabilities catalog (CVE-2026-76466 added November 20, 2026)
- CISA: BOD 26-04 implementation guidance and forensic triage steps
- NVD: CVE-2026-76466
