Attackers have exploited a critical Cisco Expressway vulnerability, CVE-2026-76466, against a Russian organization after a proof-of-concept exploit appeared on GitHub, security firm F6 reported. Cisco’s advisory still says it knows of no malicious use.
CVE-2026-76466 Gives Unauthenticated Root Command Execution on Clustered Expressway
The flaw carries a CVSS score of 9.8. It allows unauthenticated remote attackers to run commands as root through the Expressway database service and persistent cookies. Only clustered devices are affected. It impacts Cisco Expressway Core and Edge in clustered deployments.
Cisco disclosed the vulnerability on October 21. The advisory has not changed since and continues to say that Cisco is not aware of malicious use. A proof-of-concept exploit has since appeared on GitHub.
F6 Describes the Intrusion Against Two Internet-Exposed Devices
F6 says the attackers breached two internet-exposed Expressway devices running X15.5.3. From there they pivoted to two internal cluster nodes, gained root access and prepared tools for lateral movement, including custom Python scripts.
The sequence F6 reports runs from disclosure to a public proof of concept and then to an observed attack. The report is the first indication in the available coverage that the flaw is being used against a real target, which is at odds with the wording of Cisco’s unchanged advisory.
Fixed Release and Lack of Workarounds
Cisco fixed the flaw in Expressway X15.5.20. The company offers no workarounds, so upgrading is the only remediation. Organizations on Expressway X14 and earlier must migrate to a supported release to get the fix.
Clustered Deployments Define the Exposure
The vulnerability applies only to clustered devices, which narrows the exposed population to deployments that use clustering for resilience. Within that group, the attack path requires no credentials, and an internet-facing Core or Edge node is a candidate target.
Collaboration Gateways as an Internal Pivot Point
The impact is root control of collaboration gateways and a springboard into the internal network. Expressway devices sit at the boundary between internal voice and video infrastructure and the internet, so a compromised Edge node is positioned to reach hosts inside the perimeter. F6’s account of the two internal cluster nodes shows the attackers moving beyond the exposed devices as soon as they had root.
The gap between Cisco’s October advisory and F6’s report is about a month, during which a public exploit became available. Cisco’s advisory does not yet reflect the observed exploitation, and the lack of any workaround places the entire burden on the upgrade to X15.5.20 for affected clusters.
Reading the Gap Between Cisco’s Advisory and the F6 Report
Cisco’s advisory dates from October 21 and still states that the company knows of no malicious use, while F6 reports exploitation against a Russian organization after the public proof of concept appeared. The two statements are not necessarily in conflict, since Cisco’s wording reflects what it knows, and F6’s report is a third-party observation of one victim. The F6 account is specific: two internet-exposed Expressway devices running X15.5.3 were breached, and the attackers reached two internal cluster nodes and obtained root. The preparation of custom Python scripts for lateral movement suggests the operators intended to go further than the initial devices. The reporting does not identify the attackers.
Migration Requirement for Older Expressway Releases
Because X14 and earlier releases will not receive the fix, organizations still on those versions face a migration rather than a simple patch. With no workaround available, the only mitigation described is moving to X15.5.20.
F6’s report describes the attack against a Russian organization, and the reporting does not say whether the same attackers have targeted organizations elsewhere. Because a public exploit is now available on GitHub, the pool of potential attackers is not limited to the group F6 observed, and clustered Expressway deployments reachable from the internet are the devices at greatest risk until they move to the fixed release.
