Skip to content
feed: live
0dayNews
cisco

Cisco Expressway CVE-2026-76466 Exploited After PoC

F6 reports the first in-the-wild exploitation of Cisco Expressway CVE-2026-76466, a root command execution flaw, weeks after a patch and a public PoC.

Cisco Expressway CVE-2026-76466 Exploited After PoC
Image: AI-generated — conceptual illustration, not incident evidence / 0dayNews AI Cover · Generated on-site infrastructure — no external license
kilobaudDave "Kilobaud" Ferris·Published ·2 min read

Attackers are now exploiting CVE-2026-76466, a critical flaw in Cisco Expressway, a month after Cisco shipped the fix. If you run Expressway, confirm you are on a patched release and look for signs of compromise.

What was reported

According to The Hacker News, the Russian security firm F6 published a report on Thursday describing what it believes is the first in-the-wild exploitation of the flaw. The bug is rated CVSS 9.8 and lets an unauthenticated remote attacker with network access run operating system commands as root. F6 says exploitation followed the public release of a proof-of-concept exploit.

Cisco’s advisory, quoted in the same report, attributes the problem to persistent cookies and to client certificates not being validated when TLS Verify Mode is enabled for clustering. We are not describing how the flaw is triggered. The advisory and the F6 report carry that detail.

Affected and fixed versions

Per the reporting, Cisco released fixes on October 21, 2026:

  • Expressway Series X14 and earlier: migrate to a fixed release.
  • Expressway Series X15.5.3 and earlier: upgrade to X15.5.20.

What the intrusion looked like

F6 says the attackers first compromised two internet-facing Expressway devices running X15.5.3. From one of them they reached two more cluster nodes on the internal network. After getting root, they used custom Python scripts to scan the network, find SMB shares, talk to SQL Server and WinRM, and reach GitLab repositories to collect credentials and other sensitive data.

F6 noted that the scripts contain comments and fix descriptions that suggest AI-assisted development. The attack has not been attributed to any known group. The victim was a Russian organization.

What to do

  • Upgrade to the fixed release for your train, and plan a migration if you are on X14 or earlier.
  • Audit for compromise, not just version numbers. F6 published indicators of compromise, including a specific entry in the Erlang system log on affected devices. Check them in the Hacker News write-up or F6’s report.
  • If you find signs of compromise, isolate the device, scope the intrusion, and block lateral movement paths from it.

Why the cluster detail matters

Analysis: the interesting part is not the root shell, which is the expected outcome for a flaw like this. It is that a cluster of edge devices gave the attacker a bridge to the inside. A perimeter appliance that trusts its peers makes the second and third compromise cheap. F6’s own conclusion is that remediation has to be paired with segmentation and monitoring of the infrastructure itself, and that is hard to argue with.

The timeline is also a familiar one: advisory, patch, public PoC, then exploitation. The gap here was about a month, which is long enough that most teams should have been done already, and short enough that many were not.

Earlier Cisco coverage: Cisco Patches ASA/FTD VPN Zero-Day, Active Attacks and CISA Adds Cisco BroadWorks XXE Flaw to KEV. More on the Cisco hub.

Found this useful? Share it.