For: IT and collaboration teams who run Cisco Expressway-C or Expressway-E (video, voice and mobile or remote access gateways), including clustered pairs, and the partners who look after them. This article is based on Cisco's advisory, the NVD record and CISA's KEV data; it does not cover attack steps.
続報待ち:この記事は公式発表に合わせて更新します
- Who is affected
IT and collaboration teams who run Cisco Expressway-C or Expressway-E (video, voice and mobile or remote access gateways), including clustered pairs, and the partners who look after them.
- Confirmed so farSee the table ↓
- The flaw
- Affected
- Fix
1 more
- Workaround
- Not yet confirmed
- Who is exploiting the flaw, since when and how widely (not published in CISA's entry or in Cisco's advisory)
- Whether Cisco revises its advisory to reflect exploitation (not revised as of November 21)
- Ransomware use (the KEV entry says Unknown)
- What to do nowSee the steps ↓
- Find your Expressway nodes and check whether they are clustered
- Upgrade to a fixed release
- Narrow who can reach the nodes until then
1 more
- Check for signs of compromise
- Where to verify (source)All sources ↓
- Cisco
- Last checked
- as of November 21, 2026
Follow-up plans and what we checked
Cisco published the advisory on October 21, 2026 (Version 1.0, still the only revision when we checked). It said Cisco PSIRT was not aware of public announcements or malicious use. CISA added the CVE to the KEV catalog on November 20 with a federal due date of November 23, flagged for forensic triage, and its SSVC entry on the NVD record lists exploitation as active. We do not have a source that describes the attacks. Cisco's advisory and CISA's listing do not agree on exploitation; the KEV listing is the later one.
What to do today
Find your Expressway nodes and check whether they are clustered
List every Expressway-C and Expressway-E, virtual and appliance, with its version and cluster membership. Per Cisco, a device is affected when it runs a vulnerable release and is configured in a cluster. Also look for forgotten nodes at branch sites and in labs.
Upgrade to a fixed release
Per Cisco's advisory, X15.5.3 and earlier are fixed in X15.5.20. For X14 and earlier, migrate to a fixed release. Follow Cisco's upgrade guidance for clusters and plan the order so that calls and remote access keep working.
Narrow who can reach the nodes until then
Cisco lists no workaround. As a general measure, not Cisco's: confirm that the ports used for clustering between nodes are not reachable from the internet or from untrusted internal networks, and limit them to the node addresses and your management network. Judge for yourself how much this reduces the risk.
Check for signs of compromise
Because CISA lists the flaw as exploited and the start date is unknown, review the logs of the nodes and the firewalls in front of them for unexpected connections to the clustering services from addresses that are not cluster members, for unexpected configuration changes, and for unfamiliar administrator activity. No finding does not prove you are clean. If something looks wrong, isolate the node, involve Cisco support, and rotate the credentials and certificates held on the device (how to check for intrusion).
What kind of flaw this is
- CVE
- CVE-2026-76466 (Cisco Expressway Series; advisory cisco-sa-vcs-static-cred-hr7EWZ8t; bug ID CSCww27732)
- Severity
- CVSS v3.1 9.8 (CRITICAL; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Type
- Use of hard-coded credentials (CWE-798) in the database service
- Impact
- An unauthenticated remote attacker with network access can run arbitrary operating system commands as root on a clustered device (Cisco)
- Affected
- Expressway-C and Expressway-E, virtual and appliance, on a vulnerable release and configured in a cluster
- Fix
- X15.5.20 for X15.5.3 and earlier; migrate from X14 and earlier. No workaround (Cisco)
- Published
- Cisco advisory October 21, 2026 (Version 1.0)
- Exploitation
- Cisco's advisory: no known malicious use at publication. CISA KEV: added November 20, due November 23
- In short: Cisco attributes the flaw to the use of persistent cookies in the database service and to client certificates not being validated when TLS Verify Mode is enabled for clustering, and Cisco and CISA classify it as hard-coded credentials (CWE-798). An attacker who holds the cookies does not need to log in. We do not include request details.
- Why the severity is high: root on an edge collaboration gateway means control of a device that sits between the internet and your internal voice and video network.
- Our view: a flaw that needs a cluster is easy to underrate in a quick inventory. Count clusters as a separate line in your asset list, and treat any cluster member as affected until its version is confirmed.
What is known and what is not
| Item | Content | Status |
|---|---|---|
| The flaw | Hard-coded credentials in the database service of clustered Expressway | Confirmed (Cisco, NVD) |
| Affected | Expressway-C and -E on a vulnerable release, in a cluster | Confirmed (Cisco) |
| Fix | X15.5.20 for X15.5.3 and earlier; migrate from X14 and earlier | Confirmed (Cisco) |
| Workaround | None | Confirmed (Cisco) |
| Exploitation | CISA KEV since November 20; Cisco's October 21 advisory said it knew of no malicious use | KEV confirmed; the two sources differ in date |
| Who, since when, how many | Not published | Unknown |
Sources
- Cisco — Cisco Expressway Series Remote Code Execution Vulnerability (cisco-sa-vcs-static-cred-hr7EWZ8t) (October 21, 2026; affected conditions, fixed releases, no workaround)
- NVD — CVE-2026-76466 (CVSS, CWE, KEV fields)
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 20, due November 23)
Attack steps and indicators of compromise (IOCs) are not included. Last verified: November 21, 2026.
Update history
2026-11-21: First report. Based on Cisco's advisory of October 21, the NVD record and the CISA KEV data. Cisco's advisory and CISA's listing differ on exploitation; both are stated.
Read next
- Related: Exploited edge device vulnerabilities, mid-October 2026
- Same vendor: Cisco ASA and FTD VPN flaw CVE-2026-76418 (unauthenticated reload)
- Practice: Vulnerability remediation playbook / Asset inventory checklist
- Prioritizing: Deciding fix order with CVSS, EPSS and KEV
- Checking: How to check for intrusion