Cisco Expressway Flaw Gives Root Access With No Login

A hard-coded credential in the Cisco Expressway database service lets an unauthenticated attacker run commands as root on clustered nodes. Cluster mTLS does not stop it, and Cisco lists no workaround.

Published 20 November 2026, 9 pages, Mitigata Threat Research

In plain words

A flaw in Cisco Expressway, a gateway that carries phone and video calls, lets someone with no password take full control of it. Only gateways set up as a cluster are affected. The fix is a software update, and Cisco lists no temporary workaround. Cisco has not seen anyone use it yet.

For business leaders

Cisco rates this Expressway flaw critical. An unauthenticated attacker can run commands as root on clustered Expressway-C and Expressway-E nodes. It bypasses TLS Verify Mode, the cluster certificate setting many operators rely on, so that setting gives no protection. Only clustered nodes are exposed, and Cisco is not aware of malicious use. Ask your network team to confirm each gateway's version and cluster status now, because only clustered nodes on X15.5.3 and earlier are affected. Ask them to move those nodes to X15.5.20 or later, because Cisco lists no workaround. A compromised node sits between the DMZ and the internal network, so waiting leaves an attacker with root access to a gateway that can reach internal systems. If a node is compromised, CERT-In requires a report within 6 hours.

For security analysts

Technique: a persistent hard-coded cookie, classed as hard-coded credentials (CWE-798), is trusted by the Expressway database service. An attacker invokes specific RPC commands that run arbitrary OS commands as root, with no authentication. Second defect: with TLS Verify Mode set to Enabled for clustering, client certificates are not validated, so cluster mTLS does not block the attack. Identifiers: CVE-2026-76466; advisory cisco-sa-vcs-static-cred-hr7EWZ8t; bug ID CSCww27732. Score: CVSS 3.1 9.8 (Cisco); NVD analysis awaiting. Exploit status: Cisco PSIRT not aware of public announcements or malicious use; no indicators of compromise published. Affected: clustered Expressway-C and Expressway-E on X15.5.3 and earlier, including X14 and earlier. Standalone nodes not affected. Fixed in: X15.5.20 or later, or Security Hardening Release October 2026 (cisco-sa-exwy-hardening-FhcqBVcs). X14 has no fix on its train, so migrate. Workarounds: none listed by Cisco. Step 1: upgrade clustered nodes to X15.5.20 or later. Step 2: restrict cluster database and RPC ports to peer node IPs (analysis, not Cisco-stated). Step 3: detect unexpected OS processes or outbound connections from the database service. Step 4: detect RPC traffic to cluster ports from non-peer IPs. If compromised: isolate the node, rebuild from a known-good fixed image, rotate CUCM and MRA trust and cluster certificates, and report to CERT-In within 6 hours (Section 70B).

Key points

CVE ids covered: CVE-2026-76466

The full report is a PDF that opens with a work email.