A Cisco Expressway vulnerability is being exploited to take over network gateways, and US federal agencies have until November 23 to patch it. According to F6's report, reprinted by LAVX News, attackers rooted four clustered Expressway devices at a Russian organization, and F6 reported the intrusions on November 19. The flaw, tracked as CVE-2026-76466, carries a CVSS score of 9.8. CISA added it to its Known Exploited Vulnerabilities catalog on November 20, and Cisco shipped fixed releases in October.

Cisco Expressway vulnerability: which versions are affected

Cisco published its advisory on October 21, 2026. It covers Expressway-C and Expressway-E devices that run in a cluster, and releases X15.5.3 and earlier are vulnerable. The fix is X15.5.20, according to Asadria and Secure.com.

Standalone Expressway devices are not affected, according to Cisco. That makes the first check a practical one: confirm whether your Expressway pair is actually part of a cluster.

  • Vulnerable: clustered Expressway-C or Expressway-E on X15.5.3 or earlier
  • Fixed: X15.5.20 and later
  • Not affected: standalone Expressway devices, according to Cisco
  • Older X14 releases: need migration to a supported version first

How attackers reached root and moved inward

The flaw lets an unauthenticated attacker with network access run operating-system commands as root on a clustered device, through the database service. The Hacker News and the GitHub advisory both describe the bug in those terms.

F6's account describes what happened next. The attackers compromised two internet-facing devices, then pivoted to two internal cluster nodes. From there they ran Python scripts to scan SMB shares, probe SQL Server and WinRM, and pull credentials from internal GitLab repositories.

That sequence explains the risk. The edge node is the entry point, but the internal cluster nodes and everything they can reach become the real target. A single unpatched device can turn into a route to file servers, databases and source code.

The GitHub advisory frames the root cause as a hard-coded credential issue. Rescana's summary of Cisco's advisory points to persistent cookies and weak client-certificate validation when TLS Verify Mode is enabled for clustering. Cisco has not disclosed how an attacker obtains the persistent cookie, which is a precondition for the exploit. Cyberpress notes that hard-coded secrets in Cisco edge products have a record of severe outcomes.

Timeline from advisory to federal deadline

Date Event
October 21, 2026 Cisco publishes its advisory and fixed releases ship
November 5, 2026 Exploit code appears on GitHub
November 19, 2026 F6 reports four rooted devices at a Russian organization
November 20, 2026 CISA adds CVE-2026-76466 to its KEV catalog
November 23, 2026 Federal patch deadline under BOD 26-04

The gap between public exploit code and the reported attack was about two weeks. The sources reviewed describe that pattern as the kind that typically drives fast exploitation [3][4].

Cisco's October language now reads differently. Rescana quotes the advisory saying the flaws "were found during internal testing and are not known to be actively exploited." Cisco also said it found them through internal testing with existing processes and frontier AI models. That statement predates the November reports, so it no longer describes the threat.

For federal civilian agencies, the clock is short. CISA's KEV entry sets the due date at November 23, 2026, and requires forensic triage under BOD 26-04 [2]. Because the listing came on a Friday, the deadline falls on the first business day after it.

Who has been hit and what remains unknown

The only confirmed victim in the sources reviewed is a Russian organization, and none of those sources report a US victim. F6 has not tied the intrusions to a known threat actor. CISA lists ransomware use as unknown [2]. Whether other Expressway attacks have gone undetected is also an open question.

Cisco has not published per-flaw details, and it said it "may publish separate security advisories" later [6]. Defenders will rely on third-party summaries until that happens.

Analysis cited by Asadria and Techgenyz suggests the attackers' tooling may have involved AI assistance [5][8]. Treat that as a hypothesis, not a finding. The reports do not establish it, and the flaw is serious on its own terms with a 9.8 score and root access. Readers tracking the AI angle can compare it with a LiteLLM flaw CISA flagged as exploited in AI attacks.

What to do if you run clustered Expressway

Cisco lists no workaround, so patching is the main fix [9]. Work through these steps in order.

  1. Confirm your deployment. Standalone units are not affected, so identify which Expressway-C and Expressway-E devices sit in a cluster.
  2. Upgrade clustered devices to X15.5.20 or later. X14 units must first move to a supported version.
  3. Hunt for signs of compromise. Search erlang.log for the "wombat@" node string and watch for unusual cluster traffic on TCP ports 4371 and 4372. Those indicators come from the Secure.com and Techgenyz summaries rather than Cisco, so confirm them against Cisco's advisory before relying on them.
  4. Assume exposed nodes may be compromised. Review credentials that may have been stored on internet-facing or internal cluster nodes, including repository and file share access, and rotate any that may have been exposed.

Edge hardware often outlives its support window. SonicWall has ended patches for its Gen 6 firewalls and urged immediate replacement, which is a reminder that gateways without fixes become permanent exposures. Read the SonicWall story for the details.

What to watch next

Three threads will show how far this campaign goes. The first is whether Cisco publishes the separate advisories it has flagged, which could add detail on the cookie weakness. The second is whether F6 or another firm links the activity to a named group, since attribution would change how defenders read the Russian victim. The third is whether CISA's forensic triage requirement turns up intrusions inside US agencies.

Public exploit code has circulated since November 5, which lowers the effort needed for copycat attacks. Organizations that have not checked their cluster status should do it this week, while the federal deadline keeps attention on this flaw.