Skip to main content
Technical mechanism diagram: the exploitation chain behind the Cisco Expressway flaw, with the fault at Expressway RCE. Illustration: SecurityXP

Cisco Expressway Flaw Exploited Shortly After PoC Release to Breach Russian Organization

· 4 min read · Updated November 21, 2026 · SecurityXP

Key Facts

  • The company has shared the following indicators of compromise (IoCs) associated with the activity - - IP addresses geolocated: 66.179.31[.]32 and 18.130.47[.]116 - Presence of "wombat@127.0.0.1" in the Erlang system log (erlang.log) on affected Cisco Expressway devices - Python scripts staged in "/mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py" The attack has not been attributed to any known threat actor or group.
  • Attackers have exploited a critical flaw, tracked as CVE-2026-76466 (CVSS score of 9.8) in Cisco Expressway to breach a Russian organization, and they moved fast once a working exploit went public.
  • Russian security firm F6 says this is the first known case of the flaw being exploited in the wild, and it happened on Expressway X15.5.3 devices after a proof-of-concept exploit appeared on GitHub.
  • "Through one of them, they gained access to two additional cluster nodes located on the organization's internal network." Following root access, the attackers are said to have undertaken efforts to move laterally across the network and use custom Python scripts to scan the network, discover accessible SMB resources, interact with SQL Server and WinRM, and access GitLab repositories in order to exfiltrate credentials and other sensitive data.
  • Threat actors have been observed exploiting a recently disclosed critical security flaw in Cisco Expressway to breach a Russian organization shortly after the public release of a proof-of-concept (PoC) exploit.

From Public PoC to Cluster Root

The exploit tooling circulated publicly as the GitHub repository dinosn/cve-2026-76466, described as a “Python exploit and fleet detector” for the cluster database root RCE. Cisco’s own advisory carries the title “Cisco Expressway Series Remote Code Execution Vulnerability.” The gap between the PoC’s release and the intrusion was short enough that F6 dated the compromise to the immediate aftermath of publication, rather than to a long-running access operation against the two internet-facing appliances.

The jump from one perimeter device to two internal cluster nodes is the pivot that defines the case. Expressway clusters are built to trust one another for call routing and traversal, which is what made the second hop possible once root was obtained on the first pair of devices.

The company has shared the following indicators of compromise (IoCs) associated with the activity - - IP addresses geolocated: 66.179.31[.]32 and 18.130.47[.]116 - Presence of “wombat@127.0.0.1” in the Erlang system log (erlang.log) on affected Cisco Expressway devices - Python scripts staged in “/mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py” The attack has not been attributed to any known threat actor or group.

Attackers have exploited a critical flaw, tracked as CVE-2026-76466 (CVSS score of 9.8) in Cisco Expressway to breach a Russian organization, and they moved fast once a working exploit went public.

Russian security firm F6 says this is the first known case of the flaw being exploited in the wild, and it happened on Expressway X15.5.3 devices after a proof-of-concept exploit appeared on GitHub.

“Through one of them, they gained access to two additional cluster nodes located on the organization’s internal network.” Following root access, the attackers are said to have undertaken efforts to move laterally across the network and use custom Python scripts to scan the network, discover accessible SMB resources, interact with SQL Server and WinRM, and access GitLab repositories in order to exfiltrate credentials and other sensitive data.

Threat actors have been observed exploiting a recently disclosed critical security flaw in Cisco Expressway to breach a Russian organization shortly after the public release of a proof-of-concept (PoC) exploit.

After obtaining root access, the attackers began preparing tooling for further lateral movement across the infrastructure.” The attackers used custom Python scripts to scan networks, find accessible SMB resources, connect to SQL Server and WinRM, and search GitLab repositories.

“This incident demonstrates that compromise of a perimeter device can open a path for an attacker to an organization’s critical systems,” F6 said.

Analysis of the scripts indicates that they were possibly developed with assistance from artificial intelligence (AI) tools, given the presence of comments and descriptions of fixes.

Users are advised to update to the latest supported version of Cisco Expressway, audit environments for signs of compromise, isolate affected systems, determine the scope of the attack, and block potential lateral movement vectors.

Cisco shipped a fix on 21 October, so this wasn’t a zero-day by the time it got used.

Post-Exploitation: Scanning, SMB, SQL Server, WinRM, GitLab

After root access, the attackers moved laterally across the network. F6 reported that they used custom Python scripts to scan the network, discover accessible SMB resources, interact with SQL Server and WinRM, and reach GitLab repositories in order to exfiltrate credentials and other sensitive data. Analysis of those scripts indicates they were possibly developed with assistance from artificial intelligence tools, given the presence of comments and descriptions of fixes inside the code.

F6 published indicators of compromise tied to the activity:

  • IP addresses geolocated to 66.179.31[.]32 and 18.130.47[.]116
  • The string “wombat@127.0.0.1” appearing in the Erlang system log (erlang.log) on affected Cisco Expressway devices
  • Python scripts staged in the path /mnt/harddisk/i{0-9}{4}[a-zA-Z]?/*.py

The Erlang log artifact matters because Expressway’s cluster database runs on Erlang; a non-standard process identity registered against the loopback address is a direct record of the intrusion’s foothold rather than a network-side guess. The staging path pattern, anchored under /mnt/harddisk/ with a variable directory name, gives defenders a filesystem signature to sweep for on any Expressway node with shell access.

Perimeter Compromise and Segmentation

F6 framed the case around the trust boundary the attackers crossed. “This incident demonstrates that compromise of a perimeter device can open a path for an attacker to an organization’s critical systems,” the firm said, adding: “That means protection should therefore include not only timely vulnerability remediation but also properly configured segmentation and infrastructure monitoring.” The same perimeter-appliance pattern has shown up repeatedly this year, including the PHP2Shell exploitation on a Check Point gateway.

Users were advised to update to the latest supported version of Cisco Expressway, audit environments for signs of compromise, isolate affected systems, determine the scope of the attack, and block potential lateral movement vectors. No exploitation detail beyond the CVSS 9.8 cluster database path and the root execution outcome was disclosed, and F6 did not name the affected Russian organization or the volume of data exfiltrated from the GitLab repositories and SQL Server instances.

Tags: CVE-2026-76466 Cisco IoCs Presence Erlang Cisco Expressway Python

Sources & References

S SecurityXP
SecurityXP Cybersecurity News & Analysis

SecurityXP delivers cybersecurity news, vulnerability analysis, data breach reports, and threat intelligence.

Security Digest

The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.

Related Articles

Process diagram of the exploitation chain: Unpatched vCenter through Patch released, with the fault at Auth bypass.
Vulnerabilities & Exploits

VMware vCenter Authentication Bypass Exploited as Zero-Day for Over Two Months Before Patch

Broadcom's VMSA-2026-0009 fixes CVE-2026-123890, a vCenter authentication bypass exploited as a zero-day. Affected versions, fixed builds and hunting guidance.

Technical mechanism diagram of the exploitation chain: Gen 6 firewall through Perimeter risk, with the fault at Patch cutoff.
Vulnerabilities & Exploits

SonicWall Ends Gen 6 Firewall Patching, Even for Critical Flaws

Google Mandiant’s M-Trends report, published in March 2026, estimated the mean time to exploit vulnerabilities at -7 days, meaning exploitation on average…

Process diagram of the exploitation chain: SSRF in WebDialer through root access gained, with the fault at SSRF in WebDialer.
Vulnerabilities & Exploits

Cisco Unified CM Flaw CVE-2026-20230 Actively Exploited in the Wild

Cisco Unified Communications Manager has a serious vulnerability, tracked as CVE-2026-20230 (CVSS score of 8.6), that attackers are already exploiting. The...

Process diagram of the certificate trust chain: Weak key ceremony through Product audit, with the fault at Weak key ceremony.
Vulnerabilities & Exploits

Cisco Investigates Products After eMudhra Root CAs Distrusted Over Private Key Exposure

Cisco is auditing which products trust eight compromised eMudhra intermediate CAs and has published fixes and guidance for IOS XE, ASA, FMC and ISE.