SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

Cisco Expressway flaw CVE-2026-76466 exploited for root access, F6 reports

Attackers exploited the critical Cisco Expressway flaw CVE-2026-76466 after a public proof of concept appeared, gaining root on clustered nodes and reaching an internal network, according to F6.

Cisco Expressway flaw CVE-2026-76466 exploited for root access, F6 reports

Attackers have exploited a critical remote code execution flaw in Cisco Expressway, tracked as CVE-2026-76466, to gain root access on clustered devices and move into a victim’s internal network, according to Russian security firm F6. The activity was reported by SecurityWeek on November 19 and The Hacker News on November 20, 2026.

Cisco disclosed and patched the flaw on October 21, 2026. According to both outlets, the exploitation followed the publication of a proof-of-concept exploit on GitHub. Cisco’s advisory, which has not been revised since its first release, still states that its PSIRT is not aware of malicious use. SecurityWeek said it had asked Cisco for comment.

What happened

F6 says it investigated an intrusion at an unnamed Russian organization that ran Cisco Expressway in a clustered configuration. According to the reports, attackers first compromised two internet-facing Expressway devices running X15.5.3. They then reached two more cluster nodes on the internal network. The Hacker News counts four breached devices in total.

After gaining root, the attackers used custom Python scripts to scan the network, enumerate SMB shares, interact with SQL Server and WinRM, and access GitLab repositories. F6 said they took credentials and other sensitive data from those repositories. F6 also said the scripts were modified during the attack and that comments in the code suggested an AI assistant had been used. Neither outlet attributes the activity to a known threat actor. The dates of initial compromise and detection have not been disclosed.

According to Cisco’s advisory, the flaw is caused by persistent cookies in the database service and by insufficient validation of client certificates when TLS Verify Mode is enabled for clustering. An unauthenticated remote attacker with network access can abuse these weaknesses to call database RPC commands and run operating system commands as root. Cisco classifies the issue as CWE-798 (use of hard-coded credentials) and credits Stefan Aleksic of Jane Street with reporting it.

Who is affected

Cisco lists Expressway-C (Core) and Expressway-E (Edge), in both virtual and appliance form, as affected. Devices are vulnerable only when they run a vulnerable release and are configured in a cluster. Expressway is commonly deployed at the network edge to provide remote and business-to-business access for Cisco collaboration services, so Expressway-E nodes are often reachable from the internet.

Release trainStatus per Cisco
X14 and earlierMigrate to a fixed release
X15.5.3 and earlierFixed in X15.5.20

The fix is also included in Cisco’s Expressway Series Security Hardening Release for October 2026.

Severity and exploitation

Cisco rates the vulnerability critical with a CVSS 3.1 base score of 9.8. No authentication or user interaction is required. Exploitation is confirmed only by F6’s report so far. At the time of writing, none of the sources reviewed say whether CISA has added the flaw to its Known Exploited Vulnerabilities catalog. Cisco states that there are no workarounds.

F6 published indicators that The Hacker News reproduced. They include connections from IP addresses 66.179.31[.]32 and 18.130.47[.]116 and the string [email protected] in the Erlang system log (erlang.log) on affected devices. They also include Python scripts staged in directories under /mnt/harddisk/ that match the pattern i followed by four digits.

What defenders should do now

  1. Identify all Expressway-C and Expressway-E nodes and confirm whether they are clustered and which release they run.
  2. Upgrade clustered nodes to X15.5.20 or a later fixed release. Plan migration for any node on X14 or earlier.
  3. If patching must wait, F6 advises restricting TCP ports 4371 and 4372 at the firewall so that only trusted cluster node IPs can connect, according to SecurityWeek. Cisco itself lists no workaround.
  4. Review erlang.log on every node for the [email protected] string, check /mnt/harddisk/ for unexpected Python scripts, and search network logs for the published IP addresses.
  5. If indicators are found, isolate the affected nodes, rotate credentials stored in reachable systems such as GitLab and SQL Server, and look for lateral movement over SMB and WinRM.
  6. Segment Expressway clusters so cluster ports and management services are not reachable from untrusted networks.

SCVM analysis

This case follows a familiar pattern for edge appliances: the vendor ships a patch, a public proof of concept appears, and exploitation follows before many organizations have upgraded. The gap between Cisco’s October disclosure and this activity was a patching window that some operators did not use. Cisco’s statement that it has seen no malicious use reflects the advisory’s original publication and should not be read as current assurance.

The post-compromise activity is the more important signal. A root shell on a collaboration edge device gave the attackers a route to source code repositories and Windows management interfaces. Teams should treat Expressway nodes as tier-one assets, monitor them like domain-facing servers, and not assume that a clustered appliance is invisible to attackers because its cluster ports are rarely discussed.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.