The Cisco Expressway vulnerability tracked as CVE-2026-76466 has been exploited against clustered devices at a Russian organisation. The breach followed the release of public proof-of-concept code and gave the unidentified attackers root access.
Cisco Expressway vulnerability exploited in the wild
Russian security firm F6 disclosed the first observed exploitation on 18 November 2026. Attackers initially compromised two internet-exposed Cisco Expressway devices running X15.5.3, before pivoting to two additional Expressway nodes located on the organisation’s internal network.
All four devices were part of the same cluster. This configuration is important because CVE-2026-76466 affects clustered Cisco Expressway C and Expressway E deployments, rather than standalone, non-clustered systems.
After exploiting the Cisco Expressway vulnerability, the attackers obtained operating system command execution with root privileges. Root is the highest level of access on these systems, allowing an intruder to execute commands, install tools, access data and use the compromised appliance as a route into other parts of the network.
Tools prepared for lateral movement
F6 found that the attackers prepared Python scripts intended to support lateral movement beyond the compromised Expressway cluster. The tooling was designed to scan for Server Message Block resources, interact with Microsoft SQL Server and access Windows systems through Windows Remote Management, commonly known as WinRM.
The scripts also searched internal GitLab repositories for credentials and sensitive information. Access to source code repositories can expose passwords, tokens, configuration files and other secrets that may provide entry to further applications or infrastructure.
Investigators observed the scripts being modified during the operation, suggesting active development rather than the use of a completely finished toolkit. Comments within the code also indicated that an AI assistant may have been used during its preparation. No threat actor has been publicly identified or linked to the activity.
How CVE-2026-76466 enables root access
Cisco describes CVE-2026-76466 as a critical unauthenticated remote command execution vulnerability with a CVSS score of 9.8. It affects the database service used by clustered Expressway systems and can allow a remote attacker with network access to execute arbitrary operating system commands as root.
The underlying problem involves persistent cookies and insufficient validation of client certificates when clustering TLS Verify Mode is enabled. Public technical analysis focuses on the Erlang distribution service used for communication between Expressway cluster members.
On affected systems, the Erlang distribution listener operates on TCP port 4372 and authenticates peer nodes using a shared cookie. Researchers reported that affected releases contain a vendor-defined maintenance identity beginning with wombat@, together with a corresponding maintenance cookie.
In the default TLS Permissive mode, client certificates are not enforced. An attacker who can reach the service and knows the maintenance credentials can complete the Erlang handshake and issue remote procedure calls. Public proof-of-concept material demonstrates this approach by using an Erlang rpc:call request to run an operating system command as root.
The demonstrated command, which checked the effective user identifier, returned zero on an X15.3.2 cluster. On Linux-based systems, a user identifier of zero confirms root privileges. This helps explain how the attackers in the reported incident gained complete control of the affected appliances.
Affected Cisco Expressway products and fixes
The Cisco Expressway vulnerability affects virtual and physical appliance deployments of Cisco Expressway C and Expressway E when they are configured as a cluster. Cisco’s advisory does not identify standalone, non-clustered deployments as affected.
- X15.5.3 and earlier: Upgrade to X15.5.20, the first fixed release in the X15.5 train.
- X14 and earlier: Migrate to a fixed release.
- Workarounds: Cisco states that no workaround is available.
The systems compromised in the F6 investigation were running X15.5.3, which falls within the vulnerable range. Because there is no workaround, configuration changes alone cannot remove the vulnerability, although network restrictions can reduce exposure to the attack path.
Timeline from disclosure to exploitation
- 21 October 2026: Cisco published its advisory for CVE-2026-76466, provided fixed release information and stated that it was unaware of malicious use.
- Late October 2026: Public technical analysis and proof-of-concept material became available on GitHub, including exploit and detection content.
- 28 October 2026: Cal-CSIC circulated an advisory summarising the vulnerability and reported no known malicious exploitation at that time.
- 18 November 2026: F6 disclosed the first observed in-the-wild exploitation at a Russian organisation and published indicators of compromise.
- 19 November 2026: Further reporting highlighted that the attack occurred shortly after public exploit code became available.
At the time of the 19 November reporting, Cisco’s advisory had not been updated to acknowledge malicious exploitation. Its statement that no malicious use was known reflected the position when the advisory was published on 21 October, before F6 disclosed the incident.
Current exploitation status and indicators
Only one victim organisation has been publicly reported, and there is no confirmed evidence of a wider campaign. However, the availability of working exploit material lowers the technical barrier for other attackers. The combination of internet exposure, unauthenticated access and root-level command execution makes vulnerable clustered deployments a significant target.
F6 published several indicators associated with the incident. These should be treated as evidence linked to this specific case, rather than a complete list of all possible exploitation activity:
- Source IP addresses 66.179.31.32 and 18.130.47.116.
- An Erlang log entry containing nodeup,’wombat@127.0.0.1′.
- Python files matching the observed path pattern /mnt/harddisk/i {0-9}{4}[a-zA-Z]?/*.py.
- Unexpected access to the Erlang distribution service on TCP port 4372.
Actions for organisations using Expressway
Organisations should identify clustered Expressway C and E deployments and confirm their installed versions. Systems on X15.5.3 or earlier should be upgraded to X15.5.20, while deployments on X14 or earlier require migration to a fixed release.
Access to TCP ports 4371 and 4372 should be limited to trusted cluster peers. Security teams should also review erlang.log for the wombat node indicator, search for the reported Python file pattern and investigate connections involving the published IP addresses.
Because the observed attackers prepared tools for SMB, SQL Server, WinRM and GitLab access, any confirmed Expressway compromise should trigger an investigation beyond the appliances themselves. Relevant credentials, internal repositories and systems reachable from the affected cluster may also require review.
Originally reported by securityweek.com.






