# Cisco Expressway CVE-2026-76466 detection pack

Pack 1.0.0, built 19 Nov 2026 (times are Europe/London; GMT unless marked BST). Research is credited to security researchers only; this pack names no researcher or security firm.

## At a glance

| Item | Value |
| --- | --- |
| CVE | CVE-2026-76466 (Cisco bug CSCww27732, CWE-798) |
| Cisco advisory | cisco-sa-vcs-static-cred-hr7EWZ8t, "Cisco Expressway Series Remote Code Execution Vulnerability", version 1.0 Final, first published 21 Oct 2026 16:00 GMT (17:00 BST) |
| Severity | **Critical, because Cisco scores it CVSS 3.1 9.8** (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| Affected | Expressway-C and Expressway-E, virtual and appliance, on a vulnerable release **and configured in a cluster** |
| Fixed | X15.5.20 (for X15.5.3 and earlier). X14 and earlier: "Migrate to a fixed release." |
| Workarounds | Cisco: "There are no workarounds that address this vulnerability." |
| Exploitation | Exploitation reported via SecurityWeek (19 Nov 2026 13:12 GMT). Cisco's advisory v1.0 reports no known malicious use as of 21 Oct 2026, and has not been revised since. |
| CISA KEV | Not in CISA KEV (catalogue 2026.11.18, released 18 Nov 2026 19:17 GMT; rechecked 19 Nov 2026 14:40 GMT) |
| NVD | Awaiting Analysis (last modified 22 Oct 2026 23:19 UTC, 00:19 BST on 23 Oct) |

**Patch now regardless of KEV status.** Upgrade to X15.5.20; move X14 and earlier to a fixed release.

## What Cisco says

- "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."
- "This vulnerability is due to the use of persistent cookies. Additionally, there is insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering, which means that client certificates are not validated."
- "This vulnerability affects Cisco Expressway-C and Cisco Expressway-E, both virtual and appliance versions, if they are running a vulnerable release and have the devices configured in a cluster."
- Fixed release table: "X14 and earlier: Migrate to a fixed release." and "X15.5.3 and earlier: X15.5.20".
- "There are no workarounds that address this vulnerability."
- "The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory." This is version 1.0 of 21 Oct 2026; it predates the exploitation report below.
- The same fixed release, X15.5.20, also addresses Cisco's separate "Cisco Expressway Series Security Hardening Release: October 2026" advisory (cisco-sa-exwy-hardening-FhcqBVcs, High, CVSS 8.6, CVE-2026-76490 to CVE-2026-76497), which affects Expressway "regardless of device configuration". A node that is not clustered still needs the upgrade.

## What was reported (NEWS, reported via SecurityWeek)

SecurityWeek, "Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release", 19 Nov 2026 13:12 GMT. Credited to security researchers, reported via SecurityWeek:

- Attackers breached a Russian organisation shortly after a public proof of concept appeared. We do not link it.
- They first breached two internet-facing Expressway X15.5.3 nodes, then pivoted from one of them to two other cluster nodes on the internal network.
- After gaining root, they prepared custom Python scripts to scan the network, locate SMB resources, interact with SQL Server and WinRM, and search GitLab repositories, aiming to take credentials and other sensitive information. The scripts were changed during the attack.
- No victim was named and no threat actor was attributed.
- The researchers point defenders to the Erlang system log on Expressway devices.
- For organisations that cannot patch at once, the researchers recommend blocking TCP 4371 and 4372 at the firewall except from the addresses of trusted cluster nodes. This is exposure reduction, not a Cisco workaround: Cisco states there are no workarounds.
- The article says IP addresses and file paths were published elsewhere. We have not verified them against a primary source, so this pack contains **no IOCs**.

## Corrections for Website builder

1. Scope: Cisco says affected only when the Expressway is **configured in a cluster**. Do not say "all Expressway devices". A standalone node is outside this CVE's stated condition but still needs X15.5.20 for the hardening advisory.
2. Workarounds: Cisco lists **none**. Restricting TCP 4371 and 4372 to cluster peers is hardening and exposure reduction (Cisco's cluster guide describes such firewall rules for protecting the intracluster ports), not a fix.
3. Ports: TCP 4371 (cluster recovery) and TLS 4372 (cluster communication) are Cisco's cluster ports **from X8.8 onwards**. Before X8.8 the ports differ (UDP 4371, TCP 4369 to 4380, IPsec). Do not imply 4371 and 4372 cover legacy releases.
4. Exploitation wording: write "Cisco's advisory v1.0 reports no known malicious use as of 21 Oct", and "exploitation reported via SecurityWeek (19 Nov 2026)". The CISA ADP SSVC entry on the CVE record (21 Oct: Exploitation none, Automatable yes, Technical Impact total) is also stale.
5. Severity: Critical only because Cisco scores it 9.8.
6. Releases X15.5.4 to X15.5.19 are not in Cisco's table, and nothing newer than the X15.5 train is listed. Our checker reports REVIEW for them; do not call them safe.
7. KEV: not listed as of 19 Nov 2026 14:40 GMT. KEV due dates apply to US federal agencies only (BOD 26-04). Absence from KEV says nothing about whether attacks have happened.
8. The CVE record names the product "Cisco TelePresence Video Communication Server (VCS) Expressway" and lists 94 affected version entries (X8.x to X15.5.3, including one malformed duplicate, "X15.2.4."). Cisco's advisory table is the authority for fixes.
9. Credits: say "security researchers, reported via SecurityWeek". Do not name the firm the article cites, the article author or the researcher Cisco acknowledges. No proof of concept or repository links.

## Pack contents

| Path | What it is |
| --- | --- |
| `scripts/check-expressway-76466.sh` | Bash checker (offline, read only) |
| `scripts/Check-Expressway76466.ps1` | PowerShell checker, same output and exit codes byte for byte |
| `kql/cisco-expressway-cve-2026-76466-hunting.kql` | 9 hunts for Microsoft Sentinel and Defender XDR (all OUR PATTERN) |
| `sigma/*.yml` | 3 Sigma rules (all OUR PATTERN) |
| `sigma/converted/` | Kusto conversions of the Sigma rules through 5 pipelines, failures recorded |
| `tests/` | Bash and Pester tests, fixtures, static gates, negative gates, KQL parse harness, `run_all.sh` |

## Checker

The checkers never connect to anything, never run a command on the Expressway, never write a file and never print a configuration value. They print the release, a count of cluster peer addresses and a cleaned file name. Reachability tests are manual steps (below), never part of the checker.

```
bash scripts/check-expressway-76466.sh --version-string X15.5.3 --clustered yes
bash scripts/check-expressway-76466.sh --status-file xstatus.txt --config-file alternates.txt
pwsh -File scripts/Check-Expressway76466.ps1 -StatusFile xstatus.txt -Clustered no
```

Inputs:

- `--version-string S`: the release, for example `X15.5.3` (the X is optional; two or three numeric parts).
- `--status-file F`: a saved `xstatus` export. The release is read only from a line like `Version: "X15.5.3"` (the layout in Cisco TAC document 118675, from a VCS X7.2.1 example). If the file holds two different releases the result is UNKNOWN; check one node at a time.
- `--config-file F`: a saved `xConfiguration Alternates` export. Cluster state is read from `xConfiguration Alternates Peer N Address` lines (also the older `Alternates N Peer Address` layout in Cisco's VCS command reference). Any peer address set means CLUSTERED; all empty means NOT CLUSTERED; no such lines means UNKNOWN. Values are counted, never printed.
- `--clustered yes|no`: state the cluster configuration yourself instead of giving a file.
- Syslog exports are **not** parsed for the release, because Cisco does not document a release field in Expressway syslog. Give `--version-string` instead.

[UNVERIFIED] The X15 layout of `xstatus` and `xconfiguration` output is not documented in a current Cisco source we could read; the parser follows Cisco's documented older layout. Anything the checker cannot read gives UNKNOWN, never FIXED. Cluster state UNKNOWN is treated as clustered.

Collect only what is needed. A full `xconfiguration` export holds secret material (for example encrypted bind passwords and option keys). Export only `xConfiguration Alternates`, store it as you would credentials, and delete it when done.

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

## Hunts (KQL)

The KQL in this pack has NOT been run against a live tenant. Each hunt was parsed with Kusto.Language against the Microsoft Learn column lists for its table (CommonSecurityLog, Syslog, SecurityEvent, DeviceNetworkEvents, DeviceLogonEvents). That proves syntax and column names only. Fill `ExpresswayNodes` (or point it at a watchlist) first: every hunt returns nothing until you do. Tune thresholds against a normal week.

| Hunt | Table | Looks for |
| --- | --- | --- |
| Q1 OUR PATTERN | CommonSecurityLog | Cluster ports TCP 4371 and 4372 on a node reached from a non-peer address, internet sources first |
| Q2 OUR PATTERN | CommonSecurityLog | Cluster port traffic between nodes of different clusters |
| Q3 OUR PATTERN | CommonSecurityLog | A node connecting to SMB (445), WinRM (5985, 5986), SQL Server (1433) or your GitLab hosts |
| Q4 OUR PATTERN | CommonSecurityLog | Scanning breadth: many destinations or ports from a node in one hour |
| Q5 OUR PATTERN | DeviceNetworkEvents | Windows hosts receiving SMB, WinRM or SQL Server connections from a node |
| Q6 OUR PATTERN | SecurityEvent | 4624 and 4625 network logons (type 3) from a node |
| Q7 OUR PATTERN | DeviceLogonEvents | Network logons from a node |
| Q8 OUR PATTERN | Syslog | New process names in forwarded Expressway syslog, and lines mentioning python (weak lead) |
| Q9 OUR PATTERN | Syslog | Nodes whose forwarded syslog stopped or dropped sharply |

[UNVERIFIED] Expressway syslog message layouts: Q8 and Q9 use only the generic Syslog columns and compare each node with its own baseline. Port numbers for SMB, WinRM and SQL Server are the standard defaults documented by Microsoft; your SQL Server may use other ports.

## Sigma rules

| Rule | Log source | Notes |
| --- | --- | --- |
| `expressway_cluster_port_non_peer.yml` | firewall | Cluster ports from a non-peer address |
| `expressway_outbound_lateral_ports.yml` | firewall | Node to SMB, WinRM, SQL Server ports |
| `expressway_windows_network_logon.yml` | windows security | 4624 and 4625 logon type 3 from a node |

All three use the documentation range 192.0.2.0/24 (RFC 5737) as a placeholder: replace it with your node addresses. Conversions in `sigma/converted/` (pipelines: none, microsoft_xdr, microsoft_365_defender, sentinel_asim, azure_monitor) have 11 documented failures: the two firewall rules have no table mapping in the four Microsoft pipelines (8), and the logon rule's IpAddress and LogonType fields have no mapping in microsoft_xdr, microsoft_365_defender and sentinel_asim (3). Use the KQL hunts for those platforms; the azure_monitor conversion of the logon rule (SecurityEvent) is usable.

## Manual reachability checks (not part of the checker)

Run only against your own Expressway nodes, with authorisation, from a host that is **not** a cluster peer (for example a workstation and an internet vantage point you control):

```
nc -vz -w 3 NODE_ADDRESS 4371
nc -vz -w 3 NODE_ADDRESS 4372
Test-NetConnection -ComputerName NODE_ADDRESS -Port 4372
```

Both ports should be refused or time out from anything other than a peer. On each node, check System > Protection > Firewall rules > Configuration (Cisco's cluster guide: drop TCP 4371 and 4372 for all addresses, then allow each other peer, lower numbered rules first).

## Response

**Vendor advice (Cisco):** upgrade to X15.5.20; X14 and earlier must migrate to a fixed release. There are no workarounds.

**OUR ADVICE (CybaVerse, not from Cisco):**

1. Patch now, starting with clustered nodes reachable from the internet. Run the checker on every node.
2. Until patched, restrict TCP 4371 and 4372 to cluster peers at the network firewall and with the Expressway firewall rules. This reduces exposure; it is not a fix.
3. If a vulnerable clustered node was reachable on 4371 or 4372 from a non-peer, treat it as possibly compromised: preserve logs (including the Erlang system log the researchers point to, reported via SecurityWeek) before upgrading, open a case with Cisco TAC, and run Q1 to Q9 for the exposure window.
4. Rotate credentials the node holds or can reach (for example directory bind accounts), and review SQL Server, WinRM, SMB and GitLab access from node addresses.
5. An upgrade alone may not remove changes made by an attacker with root. If compromise is confirmed, rebuild with Cisco TAC guidance.

## Caveats

- The KQL in this pack has NOT been run against a live tenant.
- KEV due dates apply to US federal agencies only (BOD 26-04). Patch now regardless of KEV status.
- OUR PATTERN marks our own detection logic. [UNVERIFIED] marks layouts no current Cisco document confirms. OUR ASSUMPTION: an Expressway node does not normally open SMB, WinRM or SQL Server sessions or log on to Windows hosts; baseline before alerting.
- No IOCs, file names, process names or exploit detail are included or invented.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1046 Network Service Discovery
- T1021.002 Remote Services: SMB/Windows Admin Shares
- T1021.006 Remote Services: Windows Remote Management
- T1078 Valid Accounts

## Sources (read 19 Nov 2026, 14:29 to 14:40 GMT)

- Cisco advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-vcs-static-cred-hr7EWZ8t
- Cisco hardening advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-exwy-hardening-FhcqBVcs
- Cisco Expressway IP port usage guide, clustering connections: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-0/ip-port/exwy_b_cisco-expressway-ip-port-usage-configuration-guide-x15/exwy_m_clustering-connections.html
- Cisco Expressway cluster creation and maintenance guide X15.4, reference: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-4/cluster_creation_maint/exwy_b_cisco-expressway-cluster-creation-and-maintenance-deployment-guide-x154/exwy_m_reference.html
- Cisco TAC document 118675 (xstatus and xconfig collection): https://www.cisco.com/c/en/us/support/docs/unified-communications/telepresence-video-communication-server-vcs/118675-configure-vcs-00.html
- Cisco VCS command reference X6: https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/admin_guide/Cisco_VCS_Command_Reference_X6.pdf
- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76466
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76466
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- SecurityWeek: https://www.securityweek.com/hackers-exploit-cisco-expressway-vulnerability-soon-after-poc-release/
- Microsoft: WinRM ports https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management, SQL Server firewall https://learn.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access, SMB https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-secure-traffic, event 4624 https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4624, event 4625 https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4625
- Microsoft table schemas: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/securityevent, https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-devicenetworkevents-table, https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-devicelogonevents-table, CommonSecurityLog and Syslog table references on learn.microsoft.com
- MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/, https://attack.mitre.org/techniques/T1046/, https://attack.mitre.org/techniques/T1021/002/, https://attack.mitre.org/techniques/T1021/006/, https://attack.mitre.org/techniques/T1078/

## Test results

See `tests/run_all.sh`. Results for this build are in the delivery report.
