November 20, 2026 / news

Cisco Expressway Root RCE (CVE-2026-76466) Exploited in the Wild Two Weeks After PoC Release

Cisco Expressway CVE-2026-76466 (CVSS 9.8), an unauthenticated remote root command-execution flaw in clustered devices fixed in X15.5.20, has been exploited in the wild against a Russian organization after a public PoC, per F6.

Title: Attackers Turn a Public Proof of Concept Against Cisco Expressway, Breach Four Devices and Reach Internal Networks

Summary: Cisco Expressway CVE-2026-76466 — CVSS 9.8, patched October 21, 2026 — has now been exploited in the wild. The flaw, disclosed in advisory cisco-sa-vcs-static-cred-hr7EWZ8t as a remote code execution vulnerability in the database service of Expressway-C and Expressway-E, lets an unauthenticated remote attacker execute arbitrary operating system commands as root. Cisco traces it to the use of persistent cookies plus insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering: an attacker holding the cookies connects to the database service and invokes specific RPC commands. It affects clustered Expressway-C and Expressway-E, both virtual and appliance builds, has no workarounds, and is fixed in X15.5.20, with X14 and earlier releases told to migrate to a fixed release; the reporter was Stefan Aleksic of Jane Street, and Cisco’s PSIRT was not aware of any malicious use when the advisory went out. That changed two weeks later: Russian security company F6 reported on November 19 what appears to be the first observed in-the-wild exploitation, after a public proof-of-concept exploit had been available on GitHub since November 5. With root on two internet-facing Expressway X15.5.3 units, the intruders pivoted off one of them into two more cluster nodes inside the victim’s internal network, then ran custom Python scripts — some apparently written with AI help — for lateral movement: probing SMB shares, driving SQL Server and WinRM, and harvesting credentials and other material from the organization’s GitLab. F6’s indicators of compromise include source IP addresses 66.179.31[.]32 and 18.130.47[.]116, the string “wombat@127.0.0.1” in the Erlang system log (erlang.log) of affected devices, and Python scripts staged at /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py. The activity is not attributed to any known group. Organizations running Expressway should upgrade to a fixed release immediately and audit their clusters for these signs of compromise — the incident is a reminder that a compromised perimeter device can hand an attacker the keys to internal systems.

References:

← All news