CVE-2026-76466 in cisco expressway
LogPulse has a published detection rule for this CVE: it raises a notable when someone tries to exploit it.
What the vulnerability is
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.
Affected software: cisco expressway
Scores
- CVSS: 9.8 (critical)
- EPSS: 2.19% chance of exploitation in the next 30 days
- CISA KEV: Known exploited, listed 2026-11-20
- Published: 2026-10-21
What LogPulse has for it
- Detection rule: Yes, published
- Agent check (vulnerable version): No
- Mitigation: Yes, see below
How to mitigate it
Upgrade clustered Cisco Expressway to X15.5.20 and lock down the cluster database ports (CVE-2026-76466)
Patch or upgrade. Upgrade Cisco Expressway-C and Expressway-E to X15.5.20 or later, which fixes the cluster database service flaw that gives an unauthenticated attacker root through persistent cookies. Cisco gives no workaround and the flaw is in the CISA KEV catalog, so patch first, limit the cluster ports to the peers and check for signs of compromise.
Applies to: Cisco Expressway-C and Expressway-E (virtual and appliance) in a cluster, running X15.5.3 and earlier or X14 and earlier.
- In the Expressway web UI, check the software version on the Overview page and whether the node is part of a cluster (System, Clustering). Only clustered nodes are affected.
- Upgrade every clustered Expressway-C and Expressway-E running X15.5.3 or earlier to X15.5.20 or later (Maintenance, Upgrade), following Cisco's cluster upgrade order. Nodes on X14 or earlier must move to a fixed release: Cisco gives no fix for X14.
- Until the upgrade is done, allow TCP 4371 and 4372 on the firewall only between the cluster peers (F6 guidance, not in the Cisco advisory), and never from the internet.
- Check erlang.log on every node for the line nodeup,'[email protected]', which F6 saw on exploited devices.
- Look under /mnt/harddisk for unknown Python scripts in folders named like i1234 or i1234a, and check firewall logs for connections from 66.179.31.32 and 18.130.47.116 (F6 indicators).
- If you find signs of compromise: rebuild the nodes from a clean image on a fixed release, rotate admin, cluster and integration passwords and certificates, and check the internal systems the Expressway can reach (SMB, SQL Server, WinRM, GitLab) for logins from it.
- Review the firewall rule cisco-expressway-cluster-db-ports-from-outside in LogPulse and add the public addresses of your own cluster peers to its Trusted addresses.
Sources:
In the news
1 publication wrote about this CVE in the last 14 days, most recently on 2026-11-20.
- CISA Adds Four Known Exploited Vulnerabilities to Catalog (CISA advisories, 2026-11-20)
Source data: NIST NVD, CISA KEV and FIRST EPSS. LogPulse processes new CVEs every hour.
We build every detection with great care, but no two environments are the same. Log sources, parsing and configuration differ, so test a detection in your own environment before you rely on it.