
Attackers have exploited CVE-2026-76466, a critical flaw in Cisco Expressway, to take over devices and reach the internal network of a Russian organization, according to The Hacker News. The flaw, rated CVSS 9.8, lets an unauthenticated attacker with network access run operating-system commands as root. Cisco published the advisory and fixed releases on October 21, 2026; the exploitation report followed after a proof-of-concept exploit became public.
Cisco’s advisory says the bug comes from the use of persistent cookies, plus client certificates that are not validated when the TLS Verify Mode is enabled for clustering. An attacker holding the cookies can connect to the database service and invoke specific remote procedure call (RPC) commands. In a report published Thursday, the Russian security company F6 said it saw what appears to be the first case of in-the-wild exploitation, against Expressway X15.5.3 devices. F6 says the attackers first compromised two internet-facing devices and, through one of them, reached two more cluster nodes on the organization’s internal network. They then used custom Python scripts to scan the network, find SMB shares, interact with SQL Server and WinRM, and reach GitLab repositories to take credentials and other data. F6 says the scripts appear to have been written with AI help, because they contain explanatory comments. The attack has not been attributed to any known group.
How to check if you’re affected
Affected products, per Cisco’s advisory, are Cisco Expressway-C and Expressway-E, both virtual and appliance, running a vulnerable release and configured in a cluster. Cisco says there are no workarounds. The fixed-release table lists Expressway X14 and earlier as “migrate to a fixed release” and X15.5.3 and earlier as fixed in X15.5.20; Cisco notes the fix is also part of its October 2026 Expressway security hardening release. The Hacker News tells readers to update to the latest supported version.
F6 shared these indicators of compromise, as relayed by The Hacker News:
- Source IP addresses 66.179.31[.]32 and 18.130.47[.]116.
- The string
wombat@127.0.0.1in the Erlang system log (erlang.log) on the Expressway device. - Python scripts staged under
/mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py.
The Hacker News also lists steps from the report: audit the environment for signs of compromise, isolate affected systems, work out the scope, and block paths for lateral movement. F6 says the case shows that compromise of a perimeter device can open a path to critical systems, so segmentation and infrastructure monitoring matter alongside patching. Whether your own Expressway nodes are clustered is something to confirm in your own configuration; that check is our suggestion, not one of Cisco’s steps.
The Cisco advisory text we read says Cisco’s PSIRT was not aware of public announcements or malicious use at the time it was written, and credits Stefan Aleksic of Jane Street with reporting the flaw. It does not mention F6’s findings.
Sources
- Cisco Security Advisory: Cisco Expressway Series Remote Code Execution Vulnerability
- F6 press release on the Cisco Expressway exploitation (linked from The Hacker News; returned a bot-protection page, not read directly)
- The Hacker News: Hackers Exploit Critical Cisco Expressway Flaw, Breach Four Devices and Reach Internal Network
Related earlier coverage on Cisco edge flaws: CISA Flags Cisco BroadWorks XXE Flaw Used in AI-Driven Attack (a different product and CVE).
