Security alerts · November 20, 2026

Cisco Expressway flaw lets unauthenticated attackers take over clustered devices as root

Cisco has fixed critical flaw CVE-2026-76466 in Expressway (CVSS 9.8). An attacker without any login can run commands as root on clustered devices. Security firm F6 reports a first attack. Update to X15.5.20 or later.

Updates

November 20, 2026: On November 20, 2026, CVE-2026-76466 was added to the CISA KEV catalog, which means attackers are now actively exploiting it. If you have not updated yet, make it a priority.

What happened

On October 21, 2026, Cisco published a security advisory for a critical vulnerability, CVE-2026-76466, in the Cisco Expressway Series. This covers Expressway-C (Core) and Expressway-E (Edge) devices, which organizations mainly use for video conferencing, calling and connecting remote users to their Cisco collaboration platform.

The flaw is in the database service feature of the devices. According to Cisco, an attacker who can reach the device over the network can run operating system commands as root, the highest level of privilege, without logging in at all. Cisco has released fixed software versions.

When the advisory was published, Cisco was not aware of any malicious use. On November 20, 2026, however, The Hacker News reported that Russian security firm F6 observed what appears to be the first real-world attack, which followed the public release of a proof-of-concept exploit. According to F6, the attackers breached four Expressway devices running X15.5.3 at a Russian organization and reached its internal network. The US agency CISA has not yet added the flaw to its KEV catalog of exploited vulnerabilities.

Why it is dangerous

Cisco classifies the flaw as CWE-798, the use of hard-coded credentials. Picture a lock whose key was built in by the manufacturer and cannot be changed by the owner: whoever gets hold of that key can walk in. According to Cisco, the devices use persistent cookies (a kind of access ticket), and when TLS Verify Mode is enabled for clustering, client certificates are not actually validated. An attacker holding those cookies can connect to the database service and invoke specific remote procedure call (RPC) commands, and through them run arbitrary commands as root.

  • The attacker does not need to log in.
  • The attack works over the network. The attacker needs network access to the device and the cookies mentioned above.
  • A successful attack gives root privileges, meaning full control of the device.

Cisco rates the flaw at CVSS 9.8 out of 10 under CVSS version 3.1, which is critical. CVSS is the international severity scale. A score this high means the attack is easy, works over the network, needs no login or user interaction, and threatens data confidentiality, integrity and the availability of the device.

The EPSS score estimates the likelihood of exploitation within the next 30 days. As of November 20, 2026, it stood at about 0.4%, higher than roughly 37% of scored vulnerabilities. It is a statistical model, so fresh attack reports may not show up in it right away. The CISA KEV catalog, the list of flaws with confirmed exploitation, does not include this one yet. ENISA’s European vulnerability database lists it as EUVD-2026-107382, with no exploitation date.

Expressway-E often sits at the network edge and is reachable from the internet. The case described by F6 shows why this matters: through a compromised device, the attackers reached other cluster nodes on the internal network and tried to obtain credentials and sensitive data.

Who is affected

According to Cisco, the flaw affects Cisco Expressway-C and Expressway-E devices, both virtual and appliance, if they run a vulnerable release and are configured in a cluster. Vulnerable releases are X15.5.3 and earlier, as well as X14 and earlier.

Typical environments:

  • Expressway-E in a DMZ, used by staff working from home or by outside partners to connect to company calling and video conferencing.
  • Expressway-C on the internal network, linked to the Cisco collaboration platform.
  • Larger companies, public institutions, hospitals or schools running Cisco collaboration, often managed by an external partner.

Cisco does not list standalone devices that are not part of a cluster as vulnerable. The advisory names no other affected products. If a supplier manages your collaboration platform, ask them directly.

How to check if you are affected

Log in to the Expressway web admin interface. The software version is shown on the Status > Overview page under system information. To see whether the device is clustered, open System > Clustering: if addresses of other nodes (peers) are listed, the device is part of a cluster.

If you connect over SSH as an administrator, this command shows the version without changing anything:

xStatus SystemUnit

If the device runs X15.5.3 or earlier, or X14 or earlier, and is clustered, treat it as vulnerable. Check every node in the cluster, not just the one you usually log in to.

How to fix it

Cisco released the fix on October 21, 2026. The vendor offers no workaround, so updating is the only protection. The fix is also part of the broader Cisco Expressway Series Security Hardening Release: October 2026.

  • X15.5.3 and earlier: update to X15.5.20 or later.
  • X14 and earlier: Cisco advises migrating to a fixed release (the first fixed release is X15.5.20).

Recommended steps:

  • List all your Expressway devices and find out which ones are clustered.
  • Check for signs of compromise first (next section). Updating will not remove an attacker who is already inside.
  • Back up the configuration and follow Cisco’s cluster upgrade guide, bringing all nodes to the same fixed release.
  • Start with internet-facing Expressway-E devices, then move on to Expressway-C.
  • After the update, confirm the version on every node.

Until you can update, restrict network access to the devices to the bare minimum and monitor their traffic. This is not a substitute for the fix. If you have no service contract, Cisco says you can obtain the fixed software through Cisco TAC with the device serial number and a link to advisory cisco-sa-vcs-static-cred-hr7EWZ8t.

What if you may already be compromised

F6 published indicators of compromise, reported by The Hacker News. Check for:

  • Traffic to or from IP addresses 66.179.31[.]32 and 18.130.47[.]116 in firewall or proxy logs (the square brackets only keep the address from being clickable).
  • The entry [email protected] in the Erlang system log erlang.log on the Expressway device.
  • Python scripts (.py) in directories under /mnt/harddisk/ named with the letter “i”, four digits and optionally one more letter, such as i1234 or i1234a.

Also watch for unusual traffic from Expressway devices into the internal network: scanning, access to SMB shares, SQL Server, WinRM or GitLab repositories. According to F6, this is exactly how the attackers collected credentials and sensitive data.

If you find anything, isolate the device, determine the scope of the attack and block paths for further spread, as The Hacker News advises. Change passwords and credentials the attacker may have reached. If in doubt, bring in incident response specialists or Cisco TAC, since root access gave the attacker full control of the device.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.