Actively exploited CVSS 9.8 Security news

Cisco Expressway: attackers exploited CVE-2026-76466 soon after a proof of concept went public

On 18 November 2026 Russian security firm F6 described the first exploitation of CVE-2026-76466 in Cisco Expressway, a flaw Cisco fixed back on 21 October. Shortly after a proof-of-concept exploit appeared, attackers took over two internet-facing Expressway cluster nodes, used them to reach two more nodes on the internal network, and ran Python scripts hunting for file shares, databases and credentials. The bug gives unauthenticated root command execution (CVSS 9.8), but only on clustered devices.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Actively exploited: Cisco Expressway, CVE-2026-76466, CVSS 9.8

Key points

  • Affected: clustered Cisco Expressway-C and Expressway-E on X15.5.3 and earlier; fixed in X15.5.20, and X14 or earlier must migrate to a fixed release.
  • The bug: the cluster database service accepts an attacker who has the persistent cookies, and with TLS Verify Mode enabled it does not properly validate client certificates. Result: root commands without authentication.
  • Exploited: yes, according to F6, soon after a PoC was posted to GitHub. Cisco's advisory (version 1.0, 21 Oct) does not yet mention exploitation.
  • F6 indicators: IPs 66.179.31[.]32 and 18.130.47[.]116, the entry nodeup,'wombat@127.0.0.1' in erlang.log, scripts at /mnt/harddisk/i<4 digits>/*.py.

Vulnerabilities: CVE-2026-76466

What happened

On 18 November 2026 Russian security firm F6 published a press release on an intrusion it investigated at a company in Russia. The attackers exploited CVE-2026-76466 in Cisco Expressway devices shortly after a proof-of-concept exploit appeared on GitHub. F6 calls it the first observed exploitation of the flaw. It does not give the date of the attack or the victim's sector.

Cisco disclosed and fixed the bug on 21 October 2026 in advisory cisco-sa-vcs-static-cred-hr7EWZ8t, rated CVSS 3.1 9.8. The advisory is still at version 1.0 and says Cisco is not aware of malicious use. The flaw is not in CISA's Known Exploited Vulnerabilities catalog yet (per NVD, as of 19 Nov 2026).

Expressway is the gateway organisations use to give remote users access to Cisco video conferencing and calling (Expressway-E sits at the network edge, Expressway-C inside). That makes it a routinely internet-exposed box.

Technical details

  • Component: the Cisco Expressway database service that cluster nodes use to sync with each other.
  • Flaw type: Cisco describes a combination of persistent cookies and insufficient client certificate validation when TLS Verify Mode is enabled for clustering. An attacker who holds the cookies can connect to the service and invoke specific RPC commands. Cisco classifies it as hard-coded credentials (CWE-798).
  • Conditions: the device must be configured in a cluster and the attacker needs network access to the service. No authentication or user interaction is required.
  • Impact: arbitrary operating system commands as root.
  • How the attack unfolded, per F6: the attackers first compromised two internet-facing Expressway X15.5.3 nodes, then used one of them to exploit the same flaw on two further cluster nodes on the internal network. Their custom Python scripts scanned the network, looked for reachable SMB shares, interacted with SQL Server and WinRM, and searched GitLab repositories for credentials and sensitive data. They edited the scripts mid-attack; F6 says comments in the code suggest an AI assistant was involved.
How the Cisco Expressway cluster attack unfolded according to F61. Attacker exploits CVE-2026-76466 on two internet-facing Expressway nodes; 2. Gains root command execution and drops Python scripts; 3. Uses the same flaw to reach two more cluster nodes on the internal network; 4. Scans the network, SMB, SQL Server, WinRM and GitLab; 5. Hunts for and exfiltrates credentials and sensitive data1Attacker exploits CVE-2026-76466 ontwo internet-facing Expressway nodes2Gains root command execution anddrops Python scripts3Uses the same flaw to reach two morecluster nodes on the internal network4Scans the network, SMB, SQL Server,WinRM and GitLab5Hunts for and exfiltrates credentialsand sensitive data
Based on F6's press release (18 Nov 2026)

Who is affected

columns: Product | Versions | Status
row: Clustered Expressway-C / Expressway-E | X14 and earlier | vulnerable
row: Clustered Expressway-C / Expressway-E | X15.5.3 and earlier | vulnerable
row: Expressway-C / Expressway-E | X15.5.20 | fixed
  • Virtual and appliance Expressway-C and Expressway-E, only when configured in a cluster.
  • Cisco did not ship a separate fix for X14 and earlier; those devices must migrate to a fixed release.
  • The fix is also part of the wider October hardening release (advisory cisco-sa-exwy-hardening-FhcqBVcs).

How to tell if you were compromised

F6 published these indicators (defanged, for log and firewall searches):

66.179.31[.]32
18.130.47[.]116
erlang.log: nodeup,'wombat@127.0.0.1'
/mnt/harddisk/i[0-9]{4}[a-zA-Z]?/*.py
  1. On every Expressway node, search erlang.log for the entry nodeup,'wombat@127.0.0.1'.
  2. Check /mnt/harddisk/ for directories named i plus four digits (optionally followed by a letter) containing .py files.
  3. In firewall and NetFlow data, look for connections to the listed IPs and for unusual connections to TCP 4371–4372 from addresses outside the cluster.
  4. On the internal network, watch for SMB, WinRM and SQL Server logins originating from Expressway addresses, and unexpected GitLab access.
  5. Pull indicators out of your own logs quickly with our IOC extractor.

What to do

  1. Upgrade to X15.5.20. Cisco lists no workaround; move devices on X14 or earlier to a fixed release.
  2. Restrict the cluster ports. F6 recommends allowing TCP 4371–4372 only from the IPs of the other cluster nodes until you upgrade. It is good practice after upgrading too.
  3. Check patched devices for compromise as well. F6 warns that an attack may have happened before the fix. Run the indicator checks above on every node.
  4. If you find anything, treat the cluster as compromised: isolate the nodes, rotate every credential they could reach (AD, SQL, GitLab accounts), and rebuild the devices from a clean install.
  5. Watch your external perimeter: find out which Expressway and other edge devices are visible from the internet, and whether they should be.

Timeline

Timeline of CVE-2026-76466 in Cisco Expressway21 Oct 2026: Cisco publishes the advisory and the X15.5.20 fix; NVD record created; after 21 Oct 2026: A proof-of-concept exploit appears on GitHub (exact date not given); shortly after the PoC: Attack on a Russian company's Expressway cluster (per F6); 18 Nov 2026: F6 reports the first exploitation and publishes indicators21 Oct 2026Cisco publishes the advisoryand the X15.5.20 fix; NVDrecord createdafter 21 Oct2026A proof-of-concept exploitappears on GitHub (exact datenot given)shortly afterthe PoCAttack on a Russian company'sExpressway cluster (per F6)18 Nov 2026F6 reports the firstexploitation and publishesindicators
Based on Cisco, NVD and F6

FAQ

How do I know whether my Expressway is clustered?

Cisco's advisory does not describe a check. Look at the clustering settings in the Expressway admin interface to see whether other peers are listed, or follow Cisco's documentation for your release. Cisco says standalone devices are not affected, but upgrading is still recommended.

Is this the same flaw Cisco fixed in October?

Yes. Cisco disclosed and fixed it on 21 October 2026. What's new is documented exploitation, reported by F6 on 18 November. If you moved to X15.5.20 in October you are protected, but F6 still recommends a compromise assessment on patched devices, because an attack may have happened before the fix.

Is there a workaround?

Cisco lists none. F6 recommends limiting TCP ports 4371–4372 to the IP addresses of the other cluster nodes until you can upgrade. That blocks attacks from outside, but not an attacker who is already on the internal network.

Sources

  1. Cisco - Cisco Expressway Series Remote Code Execution Vulnerability, cisco-sa-vcs-static-cred-hr7EWZ8t (21 Oct 2026)
  2. NVD - CVE-2026-76466
  3. F6 - press release on the first exploitation of CVE-2026-76466 (18 Nov 2026, in Russian)

Spotted a mistake? Let us know and we will correct it openly.