Critical, CVSS 3.1 9.8 (Cisco)Clustered Expressway-C and Expressway-EExploitation reported via SecurityWeek

Are your clustered Cisco Expressway gateways still on X15.5.3 or earlier?

Cisco's advisory for CVE-2026-76466 covers a Critical remote code execution flaw in the database service on Cisco Expressway-C and Expressway-E, in both virtual and appliance versions, but only when the devices are configured in a cluster. Cisco scores it CVSS 3.1 9.8. An unauthenticated, remote attacker with network access can execute operating system commands as root. The fix is Expressway X15.5.20. Releases X14 and earlier must migrate to a fixed release. Cisco lists no workarounds. Standalone nodes are outside this CVE's cluster condition, but should still update to X15.5.20, which also fixes Cisco's High 8.6 hardening advisory cisco-sa-exwy-hardening-FhcqBVcs (CVE-2026-76490 to CVE-2026-76497, any configuration).

Critical (CVSS 3.1 9.8, Cisco). A later exploitation report from security researchers, reported via SecurityWeek, appeared at 13:12 GMT on 19 November 2026. Cisco's advisory v1.0 reported no known malicious use as of 21 October 2026.

SecurityWeek reports, crediting security researchers, that soon after a public proof-of-concept was released, attackers breached two internet-facing Expressway X15.5.3 nodes at a Russian organisation, moved to two internal cluster nodes, and staged Python tooling for SMB, SQL Server, WinRM and GitLab credential theft. We do not link the proof-of-concept. Cisco's advisory v1.0 reported no known malicious use as of 21 October 2026, and has not been revised since. The CVE was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 14:40 GMT on 19 November 2026 (catalogue 2026.11.18). Absence from that catalogue is not a finding that the flaw is unused. Upgrade clustered Expressways to X15.5.20, migrate anything on X14 or earlier, and still update standalone nodes to X15.5.20 for the separate hardening advisory.

At a Glance

Based on Cisco advisory cisco-sa-vcs-static-cred-hr7EWZ8t (version 1.0, first published 16:00 GMT on 21 October 2026), a later exploitation report from security researchers, reported via SecurityWeek, at 13:12 GMT on 19 November 2026, Cisco hardening advisory cisco-sa-exwy-hardening-FhcqBVcs, the official CVE record, NVD and a CISA KEV check at 14:40 GMT on 19 November 2026. Last updated 19 November 2026, 15:01 GMT.

16:00 GMT, 21 Oct

Cisco publishes advisory cisco-sa-vcs-static-cred-hr7EWZ8t, version 1.0, for CVE-2026-76466. The first fixed release is X15.5.20. Cisco lists no workarounds. Cisco's advisory v1.0 reported no known malicious use as of 21 October 2026.

17:19 GMT, 21 Oct

NVD publishes the CVE-2026-76466 record, with Cisco's CVSS 3.1 9.8 score. The record later shows status Awaiting Analysis.

13:12 GMT, 19 Nov

SecurityWeek reports, crediting security researchers, that soon after a public proof-of-concept was released, attackers breached two internet-facing Expressway X15.5.3 nodes at a Russian organisation and moved to two internal cluster nodes.

14:40 GMT, 19 Nov

CVE-2026-76466 is not in CISA KEV when we checked (catalogue version 2026.11.18, released 19:17 GMT on 18 November 2026). Cisco's advisory is still version 1.0. NVD status remains Awaiting Analysis. Recheck KEV.

What the flaw does

Wording below is from Cisco's advisory. The score and vector are Cisco's CVSS 3.1 values. The official mitigation is to upgrade to a fixed release.

  • CVE-2026-76466, CVSS 3.1 9.8 Critical (Cisco), CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco Expressway device to execute arbitrary operating system commands as root. Cisco says this is due to the use of persistent cookies (CWE-798). An attacker with possession of the cookies could connect to the database service and invoke specific remote procedure call (RPC) commands. Cisco also notes insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering. Affected products in the advisory: Cisco Expressway-C and Expressway-E, virtual and appliance, running a vulnerable release and configured in a cluster. Fixed release: X15.5.20 for X15.5.3 and earlier. X14 and earlier must migrate. Cisco lists no workarounds.

What to Do in the Next 24 Hours

Vendor advice and our advice are labelled separately. Tick both tracks.

Proactive: Find Exposure and Patch

Find every Expressway, apply Cisco's X15.5.20 fix or migrate off X14 and earlier, update standalone nodes as well for the hardening advisory, and reduce how far the cluster ports can be reached until you have patched. Restricting those ports is our advice, not a Cisco workaround, and it is not a fix.

Free Detection Pack

Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Version 1.0.0 is a read-only checker and hunt pack for CVE-2026-76466. The Sigma rules and KQL hunts are labelled OUR PATTERN.

Exit codes

CodeMeaning
0FIXED: X15.5.20 or later in the X15.5 train
2AFFECTED: X15.5.3 or earlier, clustered or cluster state unknown
3REVIEW OR UNKNOWN: release not read, between X15.5.3 and X15.5.20, or a train Cisco's table does not list
4OUTSIDE CISCO CLUSTER CONDITION: vulnerable release, not clustered (update anyway)
5USAGE OR READ ERROR
6MIGRATE: X14 or earlier, clustered or cluster state unknown

Exit code 1 is reserved and is not used. A standalone node on a vulnerable release is exit 4, not a finding that the device can be left unpatched. X15.5.20 also fixes the separate hardening advisory, which applies in any configuration.

Know the limits

  • Both checkers are read-only and offline. They never connect to a host, never run a command on an Expressway, never write files and never print configuration values.
  • The KQL has not been run against a live tenant. The Sigma rules were checked and converted, not run. Replace the documentation range 192.0.2.0/24 (RFC 5737) with your node addresses before you use the Sigma rules.
  • Reachability tests for TCP 4371 and TLS 4372 are manual steps in the README, not part of the checker. The pack contains no IOCs.

Reactive: How to Hunt (Our Advice)

This is our advice, not vendor hunting guidance. Cisco's advisory does not include detection steps. The hunting points below follow the activity from security researchers, reported via SecurityWeek, after you have confirmed the version and cluster state. Use the pack downloads above for the KQL hunts and Sigma rules, all labelled OUR PATTERN.

If you suspect compromise (our advice)

  • Isolate the affected Expressway nodes from the wider network.
  • Rebuild the devices on X15.5.20, or migrate off X14 and earlier to a fixed release. Do not rely on a cleanup of a compromised node.
  • Rotate credentials reachable from the unified communications and Active Directory environment.
  • Export logs before you make further changes, including the Erlang system logs.

Cisco Expressway CVE-2026-76466 FAQ

Short answers based on Cisco's advisory, a later exploitation report from security researchers, reported via SecurityWeek, the official CVE record, NVD and a CISA KEV check at 14:40 GMT on 19 November 2026. Last updated 19 November 2026, 15:01 GMT.

Am I affected?

You are in scope for CVE-2026-76466 if you run Cisco Expressway-C or Expressway-E, virtual or appliance, on a vulnerable release and the devices are configured in a cluster. Cisco lists X15.5.3 and earlier as vulnerable, with the first fixed release X15.5.20. Releases X14 and earlier must migrate to a fixed release. Cisco's Vulnerable Products section does not list standalone, non-clustered Expressway devices as affected by this CVE. Standalone nodes should still update to X15.5.20, which also fixes Cisco's High 8.6 hardening advisory cisco-sa-exwy-hardening-FhcqBVcs (CVE-2026-76490 to CVE-2026-76497, any configuration). Confirm the running version and whether clustering is enabled.

What is the severity?

Cisco, as the CVE assigner, scores CVE-2026-76466 CVSS 3.1 9.8 Critical, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Cisco classifies the issue as Critical. NVD status is Awaiting Analysis and NVD has not published its own score. We show Cisco's score.

Is there a patch?

Yes. Cisco's first fixed release for X15.5.3 and earlier is X15.5.20. Customers on X14 and earlier must migrate to a fixed release. The same release also fixes Cisco's High 8.6 hardening advisory cisco-sa-exwy-hardening-FhcqBVcs (CVE-2026-76490 to CVE-2026-76497), which applies regardless of device configuration. Cisco's advisory for CVE-2026-76466, version 1.0, first published at 16:00 GMT on 21 October 2026, says there are no workarounds that address this vulnerability.

Are there workarounds if I cannot patch today?

Cisco lists no workarounds. That is the vendor position, and it has not changed in advisory version 1.0. Our advice, until you can upgrade, is to find every Expressway, confirm that the cluster database ports are not reachable from the internet, and, from X8.8 onwards, restrict TCP 4371 and TLS 4372 to trusted cluster peers only. That reduces exposure and is not a fix. Treat it as a temporary control, not a substitute for X15.5.20 or a migration off X14 and earlier. Releases before X8.8 use different cluster ports.

What access does an attacker need?

Take the wording from Cisco's advisory. An unauthenticated, remote attacker with network access to an affected Expressway device could execute arbitrary operating system commands as root. Cisco says the issue is due to the use of persistent cookies, and that an attacker with possession of the cookies could connect to the database service and invoke specific remote procedure call commands. Cisco also says there is insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering. The CVSS vector is PR:N, network-reachable, with low attack complexity.

Has this been exploited?

A later exploitation report from security researchers, reported via SecurityWeek, appeared at 13:12 GMT on 19 November 2026. SecurityWeek reports that soon after a public proof-of-concept was released, attackers breached two internet-facing Expressway X15.5.3 nodes at a Russian organisation, moved to two internal cluster nodes, and staged Python tooling for SMB, SQL Server, WinRM and GitLab credential theft. We do not link the proof-of-concept. Cisco's advisory v1.0 reported no known malicious use as of 21 October 2026, and has not been revised since. CVE-2026-76466 was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 14:40 GMT on 19 November 2026 (catalogue version 2026.11.18, released 19:17 GMT on 18 November 2026). NVD status is Awaiting Analysis. We do not treat absence from KEV as a finding that the flaw is unused. Recheck KEV.

What should I do if I suspect compromise?

This is our advice, not vendor advice. Isolate the affected nodes. Review the Expressway Erlang system logs for unexpected database-service RPC activity. Look for unknown Python scripts or files on the nodes, and for outbound scanning, SMB, WinRM or SQL traffic from Expressway IP addresses. Rebuild the devices on X15.5.20, or migrate off X14 and earlier to a fixed release, and rotate credentials reachable from the unified communications and Active Directory environment. Export logs before you make further changes.

We are an MSP or manage many Expressway clusters. Where do we start?

Inventory every Expressway-C and Expressway-E, virtual and appliance, and record the version and whether the device is clustered. Patch clustered nodes on X15.5.3 and earlier to X15.5.20 first, especially any that are internet-facing, and plan migration for X14 and earlier. Standalone nodes should still update to X15.5.20 for the hardening advisory. Until then, confirm the cluster ports are not internet-reachable and, from X8.8 onwards, restrict TCP 4371 and TLS 4372 to trusted cluster peers only. That reduces exposure and is not a fix. Then review Erlang system logs, unexpected files or Python scripts, and odd outbound traffic from Expressway IPs. If you need help doing that across the estates you manage, contact CybaVerse.

Need help finding clustered Expressway gateways across the estates you manage?

CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.