A significant vulnerability in Cisco’s Expressway technology was exploited by hackers to penetrate a Russian organization shortly after a proof-of-concept (PoC) exploit was made available, as reported by cybersecurity firm F6.
Understanding the Cisco Expressway Flaw
The Expressway gateways are essential for connecting remote employees and third-party users to an organization’s collaboration services, such as video and voice calls, as well as instant messaging. The identified flaw, CVE-2026-76466, possesses a CVSS score of 9.8, indicating its severity. Remote attackers can exploit this vulnerability without authentication, provided they have network access to the affected devices. This flaw impacts both virtual and appliance versions of Expressway Core and Edge, particularly when these are configured in a cluster.
Cisco disclosed this issue on October 21, attributing it to a deficiency in the database service feature linked to persistent cookies. Attackers with access to these cookies can interact with the database service and execute root-level commands on the system.
Impact and Mitigation Recommendations
To address this security gap, Cisco recommends upgrading to Expressway X15.5.20, which resolves the vulnerability. There are no available workarounds, and customers using version X14 or earlier must transition to a fixed release. Despite the absence of public announcements regarding exploitation, a PoC exploit has surfaced on GitHub, leading to the attack investigated by F6.
F6’s analysis reveals that attackers initially breached two internet-facing Expressway X15.5.3 devices, subsequently moving to additional cluster nodes within the organization’s internal network. After obtaining root access, they utilized custom Python scripts to facilitate lateral movement within the network, targeting SMB resources, SQL Server, WinRM, and GitLab repositories to exfiltrate credentials and sensitive data.
Security Firm Insights and Recommendations
F6 noted that the attackers dynamically modified their scripts, possibly with the assistance of AI, as indicated by specific comments and descriptions found within the code. The firm did not disclose the victim’s identity nor attribute the attack to a specific threat actor.
For detection purposes, F6 highlights the importance of monitoring the Erlang system log on Expressway devices. They have also released information about IP addresses and file paths related to the attack in a Russian-language press release. Although Cisco has not provided workarounds, F6 suggests that organizations unable to apply patches should block TCP ports 4371–4372 at the firewall, allowing connections only from trusted cluster node IPs.
SecurityWeek has reached out to Cisco for comments on F6’s findings and will update the information as it becomes available.
