NewApp Monitoring is liveSign up free
AgentbeamBeta
Known exploited vulnerability · Cisco

CVE-2026-76466: Cisco Expressway Series Use of Hard-coded Credentials Vulnerability

criticalCVSS 3.1 9.8Exploited

Cisco Expressway Series (Expressway-C and Expressway-E) has a critical flaw in its database service. An unauthenticated remote attacker holding the persistent cookies can call RPC commands and run operating system commands as root. Clustered devices are affected. Cisco's fixed release for the X15.5 train is X15.5.20, and there are no workarounds. F6 reports real-world exploitation.

Published Oct 21, 2026 · Updated Nov 21, 2026 · Analysis Nov 20, 2026

What an attacker can do

The database service uses persistent cookies. When the TLS Verify Mode for clustering is Enabled, client certificates are still not validated. An attacker who has the cookies can connect to the database service and invoke specific RPC commands. Those commands execute arbitrary operating system commands as root (CWE-798, hard-coded credentials; CVSS 3.1 9.8).

F6 describes the first known exploitation, at a company in Russia, against Expressway X15.5.3 after a public proof-of-concept appeared. Attackers took over two internet-facing Expressway devices, then used one to reach two internal cluster nodes. They then ran custom Python tools for network scanning, SMB, SQL Server and WinRM access, and GitLab credential theft.

Expressway-E sits at the network edge, so root on it is a ready pivot into the internal network.

Who is affected

Cisco says Expressway-C and Expressway-E, virtual and appliance, are affected when they run a vulnerable release and are configured as a cluster. Its table lists X14 and earlier and X15.5.3 and earlier as affected. Cisco names no fixed release for X14 and earlier and says to migrate to a fixed release.

The advisory gives no version-check command. Check the running release in the Expressway web interface or through Cisco TAC, and confirm whether the node belongs to a cluster. F6's report shows an attack on X15.5.3.

How to fix it

Upgrade to Cisco Expressway X15.5.20 on the X15.5 train. The fix is also part of the Cisco Expressway Series Security Hardening Release of October 2026. For X14 and earlier, Cisco lists no fixed release: migrate to a fixed one. Cisco states there are no workarounds.

F6 suggests a stopgap if you cannot patch at once: restrict TCP ports 4371 and 4372 on the firewall to trusted cluster IP addresses only. Then run a compromise assessment, since attackers may have got in before the patch.

CISA's required action is to apply vendor mitigations under BOD 26-04 and its forensics triage requirements, or discontinue use if mitigations are unavailable. Due date 2026-11-23, binding on US federal agencies.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

How to tell if you were hit

F6 gives these indicators. In erlang.log on the Expressway, look for the line nodeup,'[email protected]'. Look for Python files under /mnt/harddisk matching /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py. Check traffic to and from 66.179.31.32 and 18.130.47.116. Review connections to TCP 4371 and 4372 from addresses outside your cluster. Also check internal systems reachable from the Expressway for scanning, SMB, WinRM, SQL Server and GitLab access. Cisco's own advisory lists no indicators.

Original advisory

From the National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.

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. An attacker with possession of the cookies could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying operating system of an affected device. Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.

Questions

Is CVE-2026-76466 exploited in the wild?

Yes. CISA added it to the KEV catalog on 2026-11-20. F6 reports the first known exploitation at a company in Russia, on Expressway X15.5.3 after a public proof-of-concept appeared. Cisco's advisory said it knew of no malicious use at publication.

Does CVE-2026-76466 affect standalone Expressway devices?

Cisco says the affected configuration is a vulnerable release that is configured in a cluster. Standalone devices are not covered by that condition. Confirm with Cisco TAC if unsure.

Is there a workaround?

Cisco says none. F6 suggests limiting TCP ports 4371 and 4372 to trusted cluster IPs on the firewall as a temporary measure until you upgrade.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

Coverage on the Beam blog

More Cisco vulnerabilities

All Cisco entries