November 19, 2026 — A critical flaw in clustered Cisco Expressway systems is reportedly being used in a real intrusion, adding urgency to a security advisory Cisco first published on October 21. Security firm F6 says it investigated attackers who used the weakness to compromise externally reachable Expressway devices at an organization in Russia and then moved to additional cluster nodes.
The vulnerability, CVE-2026-76466, carries a CVSS 3.1 base score of 9.8. Cisco describes a problem in the Expressway database service involving persistent cookies and inadequate client-certificate validation in clustering mode. In affected configurations, an attacker with network access and the relevant cookies could invoke RPC commands to execute operating-system commands as root.
Who is exposed
Cisco lists both Expressway Core and Expressway Edge, in appliance and virtual deployments, when vulnerable software is configured as a cluster. The advisory does not say that every standalone Expressway installation is vulnerable to this particular issue. Teams must confirm the product, release and clustering mode before assessing exposure.
Cisco identifies X15.5.20 as the first fixed release for X15.5.3 and earlier. Organizations running X14 or older are directed to migrate to a fixed release. The vendor says there is no workaround that resolves the flaw. Network filtering may reduce exposure but should not be presented as a substitute for patching.
What the incident report adds
According to SecurityWeek’s November 19 coverage of F6’s investigation, attackers initially reached two Internet-facing Expressway X15.5.3 systems and then accessed other cluster nodes. Researchers reported tools intended to discover SMB shares, query SQL Server, use Windows Remote Management and search GitLab-related assets. The reporting does not establish that all those tools achieved their goals or that stolen data was ultimately exfiltrated.
Cisco’s original advisory still says its incident response team was unaware of malicious use at the time of publication. That older text and F6’s newer account are not necessarily contradictory: the vendor notice had not yet incorporated the independent investigation. A confirmed scope or actor attribution beyond the reported incident has not been established.
Actions for defenders
- Identify every Expressway-C and Expressway-E node, release number, role and cluster peer, including systems accessible from the Internet.
- Schedule an upgrade to a Cisco-supported fixed release, following the vendor’s cluster maintenance guidance.
- Restrict unnecessary access to internal database and clustering services, but do not call this a complete remediation.
- Preserve and review device logs and surrounding network telemetry for unexpected connections, command execution and movement among cluster nodes.
- Investigate possible credential access if signs of compromise appear; changing passwords alone will not repair the underlying software flaw.
Sources
Cisco PSIRT — CVE-2026-76466 advisory and fixed releases; SecurityWeek — F6 incident findings, November 19, 2026.