Threat feed

CVE-2026-76466 — Cisco Expressway clustered deployments, root command execution without login (CVSS 9.8, in CISA KEV): explainer and fix (X15.5.20)

CVE-2026-76466: Cisco Expressway-C and -E in a cluster allow root command execution without login (CVSS 9.8). In CISA KEV since 20 Nov. Fixed in X15.5.20.

Published 2026-11-21 Updated 2026-11-21 Last verified 2026-11-21 6 min read
On this page

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 ↓
  1. Find your Expressway nodes and check whether they are clustered
  2. Upgrade to a fixed release
  3. Narrow who can reach the nodes until then
1 more
  1. 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

1

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.

2

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.

3

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.

4

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

Advisory summary — ADVISORY / in CISA KEV
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
9.8
CVSS v3.1
X15.5.20
Fixed release for X15.5.3 and earlier
None
Workaround listed by Cisco
Nov 23
CISA KEV federal due date
  • 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

ItemContentStatus
The flawHard-coded credentials in the database service of clustered ExpresswayConfirmed (Cisco, NVD)
AffectedExpressway-C and -E on a vulnerable release, in a clusterConfirmed (Cisco)
FixX15.5.20 for X15.5.3 and earlier; migrate from X14 and earlierConfirmed (Cisco)
WorkaroundNoneConfirmed (Cisco)
ExploitationCISA KEV since November 20; Cisco's October 21 advisory said it knew of no malicious useKEV confirmed; the two sources differ in date
Who, since when, how manyNot publishedUnknown

Sources

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.

Latest breaking reports

All breaking reports →

FAQ

QWhat is CVE-2026-76466?
A

A flaw in the database service of Cisco Expressway Series that could let an unauthenticated remote attacker with network access run arbitrary operating system commands as root (CWE-798). Cisco says it is due to the use of persistent cookies and insufficient validation of client certificates when TLS Verify Mode is enabled for clustering. CVSS v3.1 is 9.8 (critical).

QWhich devices are affected?
A

Per Cisco, Expressway-C and Expressway-E, virtual and appliance, but only those running a vulnerable release and configured in a cluster. A standalone device is not described as affected in the advisory; confirm against Cisco's advisory for your release.

QWhat is the fix, and is there a workaround?
A

Cisco lists no workaround; upgrading is the only remediation. Releases X15.5.3 and earlier are fixed in X15.5.20. For X14 and earlier, Cisco says to migrate to a fixed release. The fix is also part of Cisco's Expressway Series Security Hardening Release of October 2026.

QIs it being exploited?
A

CISA added it to its KEV catalog on 20 November 2026, with a federal due date of 23 November, which means CISA has evidence of exploitation. Cisco's advisory, first published on 21 October 2026, said Cisco PSIRT was not aware of public announcements or malicious use, and it had not been revised when we checked on 21 November. Who is exploiting it and how widely have not been published.

QDoes it matter that Cisco says it was not aware of attacks?
A

That statement dates from 21 October and reflects what Cisco knew then. The KEV listing is newer. Treat the flaw as exploited.

QWhat should I do if I cannot upgrade today?
A

Cisco gives no workaround. As a general defensive measure, not a Cisco workaround, make sure the clustering traffic between your Expressway nodes can be reached only from the other nodes and management networks, and never from untrusted networks. Judge the effect yourself and schedule the upgrade as an emergency change.