Subscribe
0%
Illustration for: Cisco Expressway flaw CVE-2026-76466 is now exploited after a public PoC. Clustered? Upgrade to X15.5.20

Cisco Expressway flaw CVE-2026-76466 is now exploited after a public PoC. Clustered? Upgrade to X15.5.20

Attackers used a public proof-of-concept for Cisco's CVSS 9.8 Expressway bug to get root on clustered devices at a Russian organization, according to security firm F6. Cisco patched it in October with no workaround, so clustered Expressway Core and Edge systems on X15.5.3 or earlier need X15.5.20 now.

Listen to this article0:00 / 4:23

A critical Cisco Expressway vulnerability patched a month ago is now being used in real attacks. Russian security firm F6 says attackers exploited CVE-2026-76466 against a Russian organization shortly after a proof-of-concept exploit appeared on GitHub, SecurityWeek reported this week. The bug is rated CVSS 9.8 and gives root command execution on affected devices.

Why it matters: Expressway is Cisco's collaboration gateway, and the first two devices breached in F6's case were internet-facing. Cisco lists no workaround. If you run a clustered Expressway and haven't upgraded since October, you are exposed to a bug with public exploit code.

Who is affected

Cisco disclosed the flaw on October 21 as part of three Expressway advisories covering 10 CVEs, according to SecurityOnline's write-up at the time.

Detail
CVE CVE-2026-76466 (CVSS 9.8; classed as use of hard-coded credentials, CWE-798)
Products Expressway Core and Expressway Edge, virtual and appliance
Condition Only when the devices are clustered
Vulnerable X14 and earlier; X15.5.3 and earlier
Fixed X15.5.20
Workaround None, per Cisco

Customers still on X14 or earlier have to move to a fixed X15 release, SecurityWeek notes. SecurityOnline credits the find to Stefan Aleksic of Jane Street; we did not see that credit in other coverage.

What the attackers did

F6's account, as relayed by SecurityWeek:

  • Attackers breached two internet-facing Expressway devices running X15.5.3, then moved from one of them to two internal nodes in the same cluster.
  • The bug gives root command execution through the Expressway database service's RPC interface. SecurityWeek describes it as exploitable by unauthenticated remote attackers with network access, though the attack also involves "persistent cookies"; none of the coverage we read explains how those are obtained.
  • After getting in, the attackers ran custom Python scripts to scan the network and harvest credentials from SMB shares, SQL Server, WinRM and GitLab repositories.
  • F6 says the scripts were modified on the fly and carried comments and fix notes suggesting an AI assistant wrote them.

F6 did not tie the activity to a known group, and the victim is unnamed. No source we read gives the exact date of the PoC release or the intrusion. A French analysis by Ayinedjimi Consultants, dated November 19, calls it the first confirmed exploitation since disclosure and estimates it happened in mid-November; that timing is the author's estimate.

When Cisco published the advisory, its PSIRT said it was not aware of public announcements or malicious use, and no public PoC existed. That has changed, but SecurityWeek says Cisco had not responded to a request for comment, and no updated Cisco statement appeared in the coverage we read. We also found no report of CISA adding the CVE to its Known Exploited Vulnerabilities catalog yet.

What to do

  1. Check whether your Expressways are clustered and which version they run. Standalone (non-clustered) devices are not affected by this CVE, per the advisory as reported.
  2. Upgrade clustered Core and Edge nodes to X15.5.20. The same release also fixes eight other Expressway hardening flaws rated up to CVSS 8.6, which Cisco said were found through internal testing including frontier AI models.
  3. Restrict TCP ports 4371–4372. F6 recommends blocking them at the firewall except between the trusted IP addresses of your own cluster nodes. That is F6's mitigation, not a Cisco workaround, but it is worth doing while you schedule the upgrade.
  4. Hunt for compromise. F6 points to Erlang system logs on the devices for signs of exploitation. Because attackers in this case pivoted inside the cluster and went after stored credentials, rotate secrets that Expressway nodes, and the hosts they can reach, have access to if you find anything unusual.

What to watch

Expect a CISA KEV listing and an updated Cisco advisory if more victims surface. With exploit code public and a pattern of attackers chaining edge-device bugs into credential theft, internet-facing clustered Expressways that are still on X15.5.3 or older should be treated as at risk.

Sources

  1. SecurityWeek — Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release securityweek.com
  2. SecurityOnline — Cisco Patches Critical Expressway Series Vulnerabilities Including Root RCE Flaw securityonline.info
  3. Ayinedjimi Consultants — CVE-2026-76466 : Cisco Expressway CVSS 9.8 exploitée en production via un PoC public ayinedjimi-consultants.fr
  4. Techbytes — Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release techbytes.app

#Cisco#Cisco Expressway#CVE-2026-76466#vulnerability#exploited#F6